Hello *,
I just learned that the configure script that comes with libftdi
doesn't fully honour any given CFLAGS or CPPFLAGS. The problem arises
from the fact that configure also creates the libftdi-config script
which in turn doesn't output the corresponding flags correctly.
The following patch for libftdi-config.in fixes the problem:
53c53
< if test "@includedir@" != "/usr/include" ; then
---
> if test "@includedir@" != /usr/include ; then
75c75
< echo $includes @CFLAGS@
---
> echo $includes
Without this patch, libftdi even fails to compile on systems where the
actual include directory differs from the installation include
directory, e.g. on my system /sw/include holds the relevant includes
from libusb etc. whereas installation of libftdi goes to /usr/local/...
Regards,
Alexander Lehmann
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
