On Wed, Feb 17, 2010 at 4:47 PM, David Brownell <[email protected]> wrote: >> Maybe it is not a real bug after all since there is a work-around to >> specify CFLAGS and LDFLAGS to get it built. > > That's how it's installed on one of my machines. "configure" needs to > be fed those flags ... otherwise "openocd" won't link. Configure it > correctly ... and all is fine. > > (FWIW this is an older Ubuntu system, where I had to install a newer > version of libftdi than "apt-get" would install.) >
Actually libftdi comes with a libftdi.pc file and libftdi-config file. libusb 0.1 comes with a libusb-config file. So I think maybe libftdi-config should be used to detect the location of libftdi directory. pkg-config could be used as well. mc...@ubuntu:~/Desktop/build/libftdi/libftdi-0.17$ libftdi-config --libs -L/usr/local/lib -lftdi -L/usr/lib -lusb mc...@ubuntu:~/Desktop/build/libftdi/libftdi-0.17$ cd mc...@ubuntu:~$ libftdi-config --libs -L/usr/local/lib -lftdi -L/usr/lib -lusb mc...@ubuntu:~$ libftdi-config --cflags -I/usr/local/include mc...@ubuntu:~$ libftdi-config --version 0.17 mc...@ubuntu:/usr/include$ pkg-config --libs libusb-1.0 -L/usr/local/lib -lusb-1.0 mc...@ubuntu:/usr/include$ pkg-config --libs libftdi -L/usr/local/lib -lftdi -lusb mc...@ubuntu:/usr/include$ pkg-config --cflags libftdi -I/usr/local/include mc...@ubuntu:/usr/include$ pkg-config --cflags libusb-1.0 -I/usr/local/include/libusb-1.0 -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
