On Mon, Jun 24, 2013 at 09:15:28AM +0800, Xiaofan Chen wrote: > On Sun, Jun 23, 2013 at 11:20 PM, Paul Fertser <[email protected]> wrote: > > On Sun, Jun 23, 2013 at 11:00:04PM +0800, Xiaofan Chen wrote: > >> Take note there is no libusb-compat under Windows, only > >> libusb-win32. > > > > Eh, now that's strange. I was sure libusb-compat is a thin emulation > > layer to allow using libusb-0.1 API by translating them to libusb-1.x > > calls, so I wasn't aware of any reasons it might not work under > > windows. > > > > I had high hopes for libusb-compat. Why doesn't it work on windows? > > Yes libusb-compat can work under Windows after some tweaking > on the build script. But then again it will only support libusb-0.1 > API and it will not support the async API extension and > isochronous transfer which already exist in libusb-win32. So > I doubt it makes much sense to offer libusb-compat under > Windows.
OpenOCD is not using libusb-win32 extensions anyway, right? So for OpenOCD users it looks like always installing plain WinUSB driver and employing libusb-compat-0.1 for the older code would be a fine solution, or am I still missing something? I doubt it makes much sense using libusb-win32 for anything at all, if one needs async support and such he better should switch to libusb-1.0, so why would anyone be using it? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ 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
