Re: Linking together .dll using .a static libraries

[Roumen Petrov]

Ralf Wildenhues wrote:
> * Roumen Petrov wrote on Fri, Feb 27, 2009 at 10:07:19PM CET:
> > LRN wrote:
> > > OK, maybe it's a stupid question, but i have to ask anyway.
> > > MinGW ships some static .a libraries. How do i link these to shared .dll
> > > libraries? It seems that libtool always performs a check (filemagic in
> > > my case) on each -lname argument, and to pass that check the library has
> > > to be "x86 archive import" or "x86 DLL", but not "x86 archive static".
> > Some of those libraries are always linked as example mingwex.
>
> Which libraries are this exactly (for various MinGW versions), and are
> any of these import libs?

quote for gcc spec file:
==========================
*lib:
%{pg:-lgmon} %{mwindows:-lgdi32 -lcomdlg32} -luser32 -lkernel32 
-ladvapi32 -lshell32

*libgcc:
%{mthreads:-lmingwthrd} -lmingw32 -lgcc -lmoldname -lmingwex -lmsvcrt
==========================

- mingwthrd: import, specific
- mingw32: static
- moldname: import (for functions without underscore)
- mingwex: static
- msvcrt+other xx*32: import (runtime)

mingwex is a specific extension. As example library add float and long 
double functions missing in msvcrt. Version 3.15 (3.14 ?) add posix 
compatible IO.


> For the non-import default-linked ones, we should probably add
> exceptions to libtool to accept them, but I'm not sure whether
> that is the right thing here.

> Thanks,
> Ralf

Roumen