On Mon, Oct 1, 2012 at 8:23 AM, Pete Batard <p...@akeo.ie> wrote: > On 2012.10.01 00:57, Xiaofan Chen wrote: >> libusbK's inf-wizard (MFC based) does bundle libusbk.dll and libusb0.dll >> for both libusb0.sys and libusbk.sys since libusbk.dll and libusb0.dll >> work with both libusb0.sys and libusbk.sys. libusbk.dll will work with >> winusb but not libusb0.dll. > > Ah, I see. So libusb0.dll can access a device that has the libusbK > driver installed, and libusbk.dll, as we already know, can access a > device that has libusb0.sys installed. > > So someone may want to use the libusb0.dll rather than the libusbK.dll > to access a libusbK.sys driven device when they choose to install the K > driver, and likewise, someone may want to use libusbk.dll rather than > libusb0.dll when trying to access a libusb0.sys driven device (the > latter being libusbx's case).
Yes. The user can now use either libusb-win32 API (libusb-0.1 API compatible) or libusb-1.0/libusbx API with libusb0.sys or libusbK.sys. > In that case, I think we always want to install both 0 and K dll, when > either K or 0 is selected a the driver. So I'm not going to modify the > K.inf template and will just add the K DLL dependency in the 0.inf one. Yes, that is good. -- Xiaofan ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
