On 3/3/15, Earnie wrote:
>> -Original Message-
>> From: David Macek [mailto:david.mace...@gmail.com]
>>
>> I think mingw should generally look for .a files (not .lib), specifically
>> .dll.a. in case
>> of DLL link stubs.
>>
>
> Binutils will handle .lib as well as .dll libraries
*not* th
> -Original Message-
> From: David Macek [mailto:david.mace...@gmail.com]
>
> I think mingw should generally look for .a files (not .lib), specifically
> .dll.a. in case
> of DLL link stubs.
>
Binutils will handle .lib as well as .dll libraries so creating import
libraries of a differe
On 2. 3. 2015 15:25, David Rysdam wrote:
> I'm lost. Is there a tutorial for this?
Try looking at these two, which seem to be still up to date:
http://www.mingw.org/wiki/createimportlibraries
http://www.mingw.org/wiki/sampledll
I think mingw should generally look for .a files (not .lib), specif
Basic problem statement: I've got a piece of software here that's
divided into "low" and "high" DLL halves. Using mingw32[1], I can
cross-compile both halves, but the high half won't link to the low
one. (The low one is standalone and works fine when I copy it over to a
Windows machine, so I know t
