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

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

On Sun, Aug 22, 2010 at 6:12 AM, Pete Batard <pb...@gm...> wrote:
> On 2010.08.21 02:07, Xiaofan Chen wrote:
>> But occasionally I forgot to put the dll.a file because
>> your binary snapshots put the dll.a import library in
>> the dll directory. I would suggest you put them to
>> put in the lib directory.
>
> I could do that. The only problem I see is that we cannot do the same
> for MS as both the import and the static library have the exact same
> name (libusb-1.0.lib). So we'd have a different behaviour between MS and
> MinGW in the snapshots.

Actually you already have a different behavior between MS and MinGW
in the snapshots. The examples of MinGW are using the dynamic
linking. If you run them, you will get a application crash due to missing
dll. Then the MSVC examples are using static linking.

But I know why they are done in this way: the MinGW build is more
or less following the Linux way, which use dynamically linking by default.

>  Also, I think most users of the snapshot are
> expected to chose whether they want to use the shared or static version
> of the library, rather than use both, so having both static and import
> in the same dir could be confusing.

I see your points and I know you tend to like static linking.
If I were you, I would probably be lazy and save my time and
only provide the import library. ;-)

> Also, the import library has had drastic modifications when full DLL
> interchangeability was set up, so if you were still using the old one,
> it is indeed not surprising that there were issues.

I will be careful now to constantly update my libusb-1.0 libraries
inside MinGW.

-- 
Xiaofan