Liviu Ionescu wrote: > my experience with windows drivers is close to null,
Then study. > and, after reading your links, my understanding is that now some of > the devices no longer work unless Zadig is installed. can you confirm this? Zadig is a tool which can be used to install drivers. It is not a driver. The important thing is that the correct USB device has the correct USB driver bound. For code which uses the libusb-1.0 API (such as the OpenOCD code covered by --enable-ftdi and libftdi1) the driver should be WinUSB. For code which uses the libusb-0.1 API (such as libftdi) the driver needs to be libusb-win32. > my build procedures already compile libusb-1, libusb-0, What exactly does libusb-0 mean? > libusb-win32 and libftdi from sources libusb-win32 isn't really neccessary for you to build - it is only neccessary for the kernel driver. > (and I have a custom pkg-config to detect them), Why? Why not do as the manual describes and use PKG_CONFIG_LIBDIR? > thank you for helping clarify some of the issues. It is no simple matter to produce a correct and useful cross-compiled version of any package. It very much requires being familiar not only with the package itself but also its dependencies and also how the respective build systems work. //Peter ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
