Re: [Mingw-users] lesson: don't have a dll and a lib in the same library path

[Greg C. <gch...@sb...>]

On 2007-12-20 22:17Z, Brandon Sneed wrote:
> This is just to document this in case anyone else runs into it...
> 
> I had to make a library (.a) from a vendor DLL.  I copied the DLL to a  
> temp directory, created a def for it in the same directory and used  
> dlltool to create a library from said DLL.  i think tried to compile  
> and link with that library and LD generated errors for every function  
> in the DLL basically saying it couldn't find _SomeFunc@n x300 or so  
> imports.
> 
> After 4 days of fighting with it, searching google (maybe with the  
> wrong search terms) etc. on a lark, i deleted the DLL and wala, it all  
> linked fine.
> 
> So.. if this is you (person reading the archives), delete that DLL!!!

What exactly were the dll and the import library named?
AIUI, using a '.dll.a' suffix would give precedence to the
import library, so you wouldn't need to delete the dll.
See the link below.

> I had previously thought that while linking to DLL's was possible, it  
> required command line parameters other than "-l<library>".

http://sourceware.org/binutils/docs-2.18/ld/WIN32.html#index-direct-linking-to-a-dll-610