From: Vincent R. <fo...@sm...> - 2010-02-17 19:37:58
|
On Tue, 16 Feb 2010 17:08:40 -0200, Cesar Strauss <ces...@gm...> wrote: > Hi, > > Since Aaron's gcc 4.4.0, when linking with OpenMP support (-fopenmp), > the module ends up depending on the pthreads DLL. > > The upstream pthreads-win32 project has the following naming convention: > > * libpthreadGC2.a for the import library > * pthreadsGC2.dll for the DLL. > > Here, "GC2" means GCC compiler, C cleanup code, soname=2. Other > combinations are possible. > > When packaging gcc 4.4.0, Aaron made the following change: > libpthreadGC2.a -> libpthread.a > This is for -lpthread to work. > > I propose going a step further, and doing: > pthreadGC2.dll -> libpthread-2.dll > libpthreadGC2.a -> libpthread.dll.a > > We already made a similar change with our mingw zlib package: > zlib1.dll -> libz-1.dll > > Cesar > Hi, What is the naming scheme used when compiling with Visual Studio ? If you modify it and it shares the same name, might there be some issues when using some binaries compiled with VS and some other with mingw ? |