This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Corinna Vinschen wrote:Boost obviously doesn't generate cyg- prefixed names, that would have to be fixed. But I can see precedence for not doing so in my /bin too. There are libpython2.4.dll, libW11.dll and libzsh-4.2.4.dll.
I just had a look into the boost packages and from my point of view they are not GTG, for various reasons. - The Cygwin naming convention of DLLs is not used:
This is fixable. I have built the package with --layout=system. Using --layout=versioned instead makes them versioned.- The DLLs are not versioned. They are on Linux:
The naming convention is different because Boost generates or can generate many combinations of libs. Static/dynamic, multi threaded/single threaded, debug/release, with or witout debug info. I do not think it would be a good idea to try to force different naming convention just for Cygwin.- The naming convention for static and dynamic link libs is not used:
Hmmm...I built boost on cygwin a while back, and I seem to remember that the 'gcc' toolset "did the right thing" on cygwin (but I could be wrong). Is it possible that somebody broke the gcc toolset's cygwin support in the recent (last week) Boost-1.33 release?
-- Chuck
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |