How can I decode the boost library naming?

I tried to find out that gd means in boost library name and I only found two other people looking for the same thing.

I suppose it should be a place where this is clearly documented and I would like to find it.

mt - multitheaded, get it with bjam threading=multi
s - bjam runtime-link=static
g - using debug versions of the standard and runtime support libraries. what bjam switch???
d - debug bjam variant=debug

Update

How do I control what bjam switches controls the above variants? In fact the only one that I wasn't able to identify is the g.

+9 A:

See Boost getting started windows section 6.3 naming and section 6.1 on Unix naming

Mark 2010-04-26 16:47:22

Thanks, the help almost solved my issue, now it remained only one question: what bjam switch does trigger the `g`?

Sorin Sbarnea 2010-04-27 08:35:30

see 5.3.4 - The option “--build-type=complete” causes bjam to build all supported variants of the libraries.

Mark 2010-04-27 09:38:58

@Mark, Thanks, I am aware about complete variant, but the idea was to minimize the disk space and build only the things I need/want. Fortunately the `g` switch is enabled by default and I obtained the minimal build I was looking for. Still I would like to know how can you disable it in order to document this for others.

Sorin Sbarnea 2010-04-27 13:54:12

The basic set of built-in features, which is what you specify on the command line (feature=value), are described in the BBv2 documentation (see builtin features). I don't know if we already updated the getting started guide in the upcoming 1.43 release but there is an outstanding documentation change to add those built-in option descriptions to the getting started guide for quicker access.

GrafikRobot 2010-04-27 12:27:30

I am pretty sure that in 1.43, the table of those decoration letters includes the corresponding Boost.Build feature.

Vladimir Prus 2010-05-03 00:53:37

ansaurus

tags:

views:

answers:

How can I decode the boost library naming?

Update

related questions