Re: [boost] Build statically linked boost libs *-vc90-mt-sgd.lib

From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-03-26 09:41:33

Richard Crossley wrote:

> 
>> -----Original Message-----
>> From: boost-bounces_at_[hidden] [mailto:boost-
>> bounces_at_[hidden]] On Behalf Of Vladimir Prus
>> Sent: 26 March 2008 12:04
>> To: boost_at_[hidden]
>> 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