Linking together .dll using .a static libraries (2)

2009-11-05 Thread hanro
I want to explain the question a bit more. I have in a .dll library implemented, e.g.: FreeContextBuffer(NULL); For this function I need to refer to libsecur32.a. How can I do that? libhello_la_LDFLAGS = -no-undefined -avoid-version -lsecur32 does not work with cygwin. Thanks for help Hanro

Re: Linking together .dll using .a static libraries

2009-02-28 Thread Ralf Wildenhues
* 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

Re: Linking together .dll using .a static libraries

2009-02-28 Thread 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

Re: Linking together .dll using .a static libraries

2009-02-27 Thread Roumen Petrov
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

Linking together .dll using .a static libraries

2009-02-26 Thread LRN
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