Re: MinGW link against an MS Windows import library

[Bill Jones]

I don't think that linking directly against a DLL under Windows is a 
good idea (or even possible).  From 
http://blogs.msdn.com/oldnewthing/archive/2004/01/12/57833.aspx it would 
appear that the LIB file should be used to account for any "decorations" 
added to the exports.

wtj

Earnie Boyd wrote:
> Tim Van Holder wrote:
>
> > Bill Jones wrote:
> >
> > > So the basic question is how do I specify a static import library 
> > > with a *.lib extension to be used by libtool for resolving the 
> > > symbols provided by a non-libtool DLL when building a dependent DLL 
> > > with libtool?
> >
> >
> >
> > The trivial solution is of course to make a copy of the third-party .lib
> > file with a .a extension (the file format is identical anyway).
> > Alternatively, you may be able to create a fresh .a from the DLL using
> > 'dllwrap --implib <dllname> -o <libname>', but it's likely that that
> > won't have all the necessary symbols.
>
>
> Or just use the dll itself in the link.  Note if the library references 
> C++ objects, then you are going to be hard pressed for an easy 
> solution.  See www.mingw.org and it's list archives for more information.
>
> Earnie

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    Bill Jones                                   address@hidden
    Mail Stop 125                       Data Analysis and Imaging Branch
    15 Langley Boulevard                  Systems Engineering Competency
    NASA Langley Research Center                Building 1268, Room 1038
    Hampton, VA  23681-2199                        Phone +1 757 864-5318
                                                     Fax +1 757 864-7635
                                             http://geolab.larc.nasa.gov