Re: [Libusb-devel] libusb-1.0 Windows backend when WinUSB is afilter driver

[Xiaofan C. <xia...@gm...>]

On Thu, Aug 19, 2010 at 11:01 AM, Michael Plante
<mic...@gm...> wrote:
> Xiaofan Chen wrote:
>>> This particular part may be a .Net problem or my problem. I was putting
>>> the 32bit libusb-1.0.dll in the same directory of benchmarkcon.exe. Maybe
>>> I should have put the 64bit one to see if that helps. I will check again.
>
>
> Would any user ever have a 32bit libusb-1.0.dll on a 64-bit OS?  If so, is
> that going to need a suffix?

Yes there are many 32bit applications even on 64bit OS.

No need a suffix. 32bit DLLs are installed to windows\syswow64 directory.
64bit DLLs are installed to windows\system32 directory.

You can look at libusb-win32 for an example. For 64bit OS, you need
64bit driver libusb0.sys, but we provide both 32bit libusb0.dll
(which goes to windows\syswow64) and 64bit libusb0.dll
(which goes to windows\system32). It is the same for
WinUSB.

The older version of libusb-win32 (0.1.12.x) does use the
prefix for both the 64bit driver and the 64bit dll. But we think
this is not a good idea. We would use similar scheme like
WinUSB (no prefix for 64bit DLL and 64bit driver).

Right now I have not seen an installer package for libusb-1.0
for Windows. The binary snapshot is not a full-fledge deployment
package. The Zadig utility is not either (only the driver part).
Maybe an installer package can be used to deploy
libusb-1.0 Windows. It can have several parts, one part is to deploy
the dll, one part is to install the development files (header
and static/import libraries), one part is for driver installation.
Right now all the individual parts are kind of ready, just
need an installer (say using Inno Setup).


-- 
Xiaofan