On Tue, Jun 25, 2013 at 9:32 PM, Paul Fertser <[email protected]> wrote:
> By unifying the API I just meant that a packager (Freddie) might want
> to compile OpenOCD against the compat-layer so that OpenOCD binaries
> would use only libusbx to communicate with the OS services (not both
> libusb-0.1 and libusbx as it does currently).
As mentioned before, there is no libusb-compat-0.1 as the libusb
0.1 API provider for Windows, there is only libusb-win32 as the
libusb-0.1 API provider under Windows. So in reality, Freddie
may still have to use libusb-0.1 and libusbx as of now.
On the other hand, if we look at Freddie's build configuration, other
than vsllink, usbprog, rlink, ulink and armjtagew,
ft2232_libftdi will also pull in libftdi-0.x and thus pull in
libusb0.dll. So we may have to either remove ft2232_libftdi
(to use the new ftdi driver) or move that to libftdi-1.0.
presto_libftdi and usb_blaster_libftdi again need to be
migrated to libftdi-1.0 or move to libusb-1.0 directly.
../configure --host=i686-w64-mingw32 --enable-amtjtagaccel
--enable-arm-jtag-ew --enable-ft2232_libftdi --enable-ftdi
--enable-gw16012 --enable-jlink --enable-opendous --enable-osbdm
--enable-parport --disable-parport-ppdev
--enable-parport-giveio --enable-presto_libftdi
--enable-remote-bitbang --enable-rlink --enable-stlink
--enable-ti-icdi --enable-ulink --enable-usb_blaster_libftdi
--enable-usbprog --enable-vsllink
To move from libftdi-0.x to libftdi-1.0 should not be too difficult
as the API is mostly compatible, the major change is the
addition of async API and the change of the library name
to libftdi1.
--
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
