On Mon, Aug 2, 2010 at 7:34 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Mon, Aug 2, 2010 at 6:26 PM, Peter Stuge <pe...@stuge.se> wrote: >> The libusb-1.0 dir in CFLAGS is a workaround for a bug in how libftdi >> uses libusb-1.0. libftdi should do #include <libusb-1.0/libusb.h> but >> does #include <libusb.h> which is wrong. This forces all libftdi >> users to mess with include paths, to add the directory that libftdi >> happened to be built with, and this is clearly *not* how things are >> supposed to work. libftdi should be fixed. > > This may not be quite true. libftdi-1.0 will try to get libusb-1.0 CFLAGS > from pkg-config data (libusb-1.0.pc). libftdi (0.1) will try to get > libusb CFLAGS from pkg-config data (libusb.pc) or libusb-config. > I think it should work fine. > >> cd libftdi-1.0 && ../openocd/bootstrap && ./configure \ >> --prefix=/tmp/test --disable-libftdipp --disable-python-binding \ >> --without-examples && make install && cd ..
I see. You are using the autoconf scripts. The libftdi-1.0 developers are mainly using CMake. The autoconf scripts will be removed sooner or later as far as I know and there may be potentially problems with the scripts. http://developer.intra2net.com/mailarchive/html/libftdi/2010/msg00344.html -- Xiaofan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
