[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

4. Installation

Flite consist simple of a set of C files. GNU configure is used to configure the engine and will work on most major architectures.

In general, the following should build the system

 
tar zxvf flite-XXX.tar.gz
cd flite-XXX
./configure
make

However you will need to explicitly call GNU make gmake if code make is not GNU make on your system.

The configuration process build a file `config/config' which under some circumstances may need to be edited, e.g. to add unusual options or dealing with cross compilation.

On Linux systems, we also support shared libraries which are useful for keeping space down when multiple different application are linked to the flite libraries. For development we strong discourage use of shared libraries as it is too easy to either not set them up correctly or accidentally pick up the wrong version. But for installation they are definitely encouraged. That is if you are just going to make and install they are good but unless you know what LD_LIBRARY_PATH does, it may be better to use static libraries (the default) if you are changing C code or building your own voices.

 
./configure --enable-shared
make

This will build both shared and static versions of the libraries but will link the executables to the shared libraries thus you will need to install the libraries in a place that your dynamic linker will find them (cf. /etc/ld.so.conf) or set LD_LIBRARY_PATH appropriately.


[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by Debian/IA64 non-US Build Daemon on September, 5 2005 using texi2html 1.76.