#1907 closed Bugs (fixed)
name of library files on mingw
Reported by: | Owned by: | Vladimir Prus | |
---|---|---|---|
Milestone: | Boost 1.42.0 | Component: | build |
Version: | Boost 1.35.0 | Severity: | Problem |
Keywords: | Cc: |
Description
When linking with mingw, a -lxxx option leads to the following files being searched, in order: 1) libxxx.dll.a 2) xxx.dll.a 3) libxxx.a (this should be the static lib) 4) <prefix>xxx.dll (e.g. cygxxx.dll on cygwin) 5) libxxx.dll 6) xxx.dll
However, boost's build system doesn't follow mingw's convention and produces: libxxx.lib (the static lib) xxx.lib (the dynamic import lib) xxx.dll
This means mingw will never find the files of the static lib and dynamic import lib. Hopefully, mingw has the ability to link directly against the dll file (providing it exists), and that's actually the one it will always pick, as the last file looked for is xxx.dll.
Change History (6)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Component: | Building Boost → build |
---|---|
Owner: | set to |
comment:3 by , 13 years ago
Milestone: | To Be Determined → Boost 1.42.0 |
---|
comment:4 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 by , 13 years ago
Thanks a lot for revisiting this old issue. The new libnames in svn changeset/revision 60062 look good :)
comment:6 by , 13 years ago
Thanks for checking. I've now added this fix to 1.43 release notes, guess it's all done.
As i just saw in gcc.jam (boost build v2, 1.35), the search pattern is different with -Bstatic: it looks for libxxx.a, then xxx.lib.