Re: MinGW & library_names

[Bob Friesenhahn]

On Thu, 30 Sep 2004, Peter O'Gorman wrote:
> Isn't this what the dlname variable is for in the .la. Is the dlname being 
> set incorrectly or not at all? Or is it being used incorrectly?
>
> From looking at the code ltdl first tries to open the old_library, then if 
> that fails it tries the dlname, you'd like it to stop opening old_library I 
> guess? The problem seems to be that it tries to open old_library using all 
> the available loaders, imo it should only be trying the preopen loader.

Maybe I have not read enough code.

In the .la file, the entries are similar to

dlname='tiff.dll'
library_names='tiff.dll.a'
old_library='tiff.a'
dependency_libs='-L/bla /bla/bla/libGraphicsMagick.la ... -lgdi32 ... -lm ...

Here is an annotated run based on some hacked libltdl code which is 
trained to only load DLL files but report both excluded and observed 
requests:

Loading "c:/home/bfriesen/mingw/GraphicsMagick-8-modules/coders/.libs/tiff.dll" 
...
Excluded "tiff.a"
Excluded "libltdl.a"
Loading "libm.dll" ...
Loading "libgdi32.dll" ...
Loading "libz.dll" ...
Excluded "libltdl.a"
Loading "libm.dll" ...
Loading "libgdi32.dll" ...
Loading "libz.dll" ...
Excluded "libGraphicsMagick.a"

So it is clear that libltdl attempts to load essentially anything that 
looks like a library from the .la file.

I am not sure why I thought that it was loading the .dll.a file.  It 
does seem like it is loading from the old_library field instead.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen