Build statically linked boost libs *-vc90-mt-sgd.lib
Hi, Feeling stupid... How do I generate the statically linked *-vc90-mt-sg*.lib series of libraries? I've run: bjam debug release link=static toolset=msvc stage --build-dir=K:\Temp\BoostBuild Against the 1.35 R2 source Which, for example, gives me the following in the stage\lib directory libboost_*-vc90-mt-1_35.lib libboost_*-vc90-mt-gd-1_35.lib libboost_*-vc90-mt-gd.lib libboost_*-vc90-mt.lib Regards, Richard.
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost- bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: 26 March 2008 12:04 To: boost@lists.boost.org Subject: Re: [boost] Build statically linked boost libs *-vc90-mt- sgd.lib
Richard Crossley wrote:
Hi,
Feeling stupid... How do I generate the statically linked *-vc90-mt-sg*.lib series of
's' is not statically linked, it's static runtime.
- Volodya
I'll rephrase it then. How do I generate the libboost-*-vc90-mt-sg.lib and libboost-*-vc90-mt-sgd.lib variants? I can see that adding the link=static option generates a separate tree in the build directory. However the ABI naming of the resultant staged libraries appears to remain the same. Richard.
Richard Crossley wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost- bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: 26 March 2008 12:04 To: boost@lists.boost.org Subject: Re: [boost] Build statically linked boost libs *-vc90-mt- sgd.lib
Richard Crossley wrote:
Hi,
Feeling stupid... How do I generate the statically linked *-vc90-mt-sg*.lib series of
's' is not statically linked, it's static runtime.
- Volodya
I'll rephrase it then.
How do I generate the libboost-*-vc90-mt-sg.lib and libboost-*-vc90-mt-sgd.lib variants?
The "lib" prefix is for static libraries. Use link=static The 's' letter is to static linking to runtime. Use runtime-link=static The 'd' is debug, use variant=debug The 'g' is using debug runtime, I think it's included in 'debug' variant already. If not runtime-debugging=on will help.
I can see that adding the link=static option generates a separate tree in the build directory. However the ABI naming of the resultant staged libraries appears to remain the same.
What is "ABI naming" and why do you expect it to change? - Volodya
Thanks! The runtime-link=static is what I was missing. By ABI naming I meant the 'sdg' part of the library name, referred to on the Getting Started page as the 'ABI tag' and I understand now that with link=static this portion shouldn't have changed. In my defence... It's been a long time since I needed to rebuild the boost libraries and things seemed to have changed; the Getting Started page identifies the potential library variants but not, as far as I can see, the options required to generate them without looking in to the Boost Build documentation and even then I have to know that I'm looking for a 'Builtin' feature. Regardless, I really don't want to have to understand the internals of the build system just to change the linking method. I just saw the link=shared under Static and Shared libraries in the Boost Build docs and incorrectly jumped to the conclusion that was what I required. Also it's not obvious that if you run bjam --help from outside the boost directory structure ("Please consult the documentation at 'http://www.boost.org'.") that a useful help message with the information I required would have been produced if it was run from within! Many thanks for your help, Richard.
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost- bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: 26 March 2008 13:42 To: boost@lists.boost.org Subject: Re: [boost] Build statically linked boost libs *-vc90-mt- sgd.lib
Richard Crossley wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost- bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: 26 March 2008 12:04 To: boost@lists.boost.org Subject: Re: [boost] Build statically linked boost libs *-vc90-mt- sgd.lib
Richard Crossley wrote:
Hi,
Feeling stupid... How do I generate the statically linked *-vc90-mt-sg*.lib series
of
's' is not statically linked, it's static runtime.
- Volodya
I'll rephrase it then.
How do I generate the libboost-*-vc90-mt-sg.lib and libboost-*-vc90-mt-sgd.lib variants?
The "lib" prefix is for static libraries. Use link=static The 's' letter is to static linking to runtime. Use runtime-link=static The 'd' is debug, use variant=debug The 'g' is using debug runtime, I think it's included in 'debug' variant already. If not runtime-debugging=on will help.
I can see that adding the link=static option generates a separate tree in the build directory. However the ABI naming of the resultant staged libraries appears to remain the same.
What is "ABI naming" and why do you expect it to change?
- Volodya
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Richard Crossley wrote:
Thanks!
The runtime-link=static is what I was missing.
By ABI naming I meant the 'sdg' part of the library name, referred to on the Getting Started page as the 'ABI tag' and I understand now that with link=static this portion shouldn't have changed.
In my defence... It's been a long time since I needed to rebuild the boost libraries and things seemed to have changed; the Getting Started page identifies the potential library variants but not, as far as I can see, the options required to generate them
Maybe, GS should actually list those options. - Volodya
participants (2)
-
Richard Crossley -
Vladimir Prus