hi Ian,
you're certainly right -- my first flite installation was under SuSE, and I haven't used the external since I switched to debian ;-) the directories hard-coded in the makefile are just hacks: i'll try and get around to changing them (probably adding '--with-flite-includes' and '--with-flite-libs' options to ./configure) this weekend.
in the meantime, you can use the environment variable CPPFLAGS to use the debian flite directory:
bash$ export CPPFLAGS="-I/usr/include/flite"
... or simply:
bash$ ./configure CPPFLAGS="-I/usr/include/flite"
flite needs a serious overhaul; i'd like to get it working in realtime (failing that, at least running in its own thread), but I just don't grok the flite API, it seems...
marmosets, Bryan
On 31 May 2004 at 19:27:35, Ian Smith-Heisters wrote:
Hi Bryan, list,
I'm not sure what the status of the flite external is these days, but I just compiled 0.01 on debian and have a suggestion for the makefile. On my debian system the flite headers (flite.h) are in /usr/include/flite where apt-get put them. Invoking configure like this: "./configure --with-flite-dir=/usr/include/flite" still yeilds a "flite.h not found" error because of lines 2636 and 2637 in the configure, which are "IFLAGS="$IFLAGS -I${FLITE_DIR}/include" LFLAGS="$LFLAGS -L${FLITE_DIR}/lib"" or something like that (I only have an altered version on hand so that's from memory, but the line numbers are certainly correct). To install on my system, and I suspect most apt-get managed systems, I needed to remove the inlcude and lib subdirectories from these statements. I just thought there might be some way to make this easier or more straightforward would is needed, as I only happened across these lines by dumb luck.
Thanks,
Ian Smith-Heisters
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev