On Wed, Jul 3, 2013 at 9:08 AM, Pete Batard <[email protected]> wrote: > By the way, is there an option to specify libftdi 1.0 over 0.x? Right > now I'm replacing the -lftdi with -lftdi1 in configure.ac & Makefile.am, > but I'm wondering if I'm missing something in terms of conf. >
Yes it is good to migrate from libftdi-0.x to libftdi-1.0 if it is available in the system or the user specify it. However, in this case, you are using the new libusb-1.0 API based ftdi jtag driver (interface/ftdi/olimex-jtag-tiny.cfg), it does not use libftdi at all, rather it directly use libusb-1.0 API. So you can just build OpenOCD with --enable-ftdi and skip --enable-ft2232_libftdi, then you will not need to care about libftdi-0.x or libftdi-1.0 at all. Ref: the new ftdi driver uses libusb-1.0 sync/async API http://repo.or.cz/w/openocd.git/blob/HEAD:/src/jtag/drivers/ftdi.c http://repo.or.cz/w/openocd.git/blob/HEAD:/src/jtag/drivers/mpsse.c -- Xiaofan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
