Boost logo

Boost-Build :

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2006-10-27 08:00:41

While continuing the comparison of bbv1 bbv2 install targets,
I found some more odd looking combinations.

I did my tests on a w2k machine, using msvc-7.1 on the RC_1_34_0

1) No unversioned libraries are created in the install path.

2) No static versions, that link against static runtime are

3) When creating debug versions, the tag indicates they are
    against the non-debug runtimes. However this is only when
    building the default variants. Specifying them explicitly
    tags them correctly.

I.e.: default
bjam --v2 install

gives e.g.:

boost_thread-vc71-mt-d-1_34.dll --> -gd- expected!
boost_thread-vc71-mt-d-1_34.lib --> -gd- expected!

libboost_thread-vc71-mt-d-1_34.lib --> -gd- expected!

But when explicitely specified on command line (in two separate runs) as

bjam --v2 install link=shared variant=debug,release
bjam --v2 install link=static runtime-link=static,shared

this produces (almost) the same (correct) combinations than
the default of bbv1 did. In particular the tagging of -gd-
also is as expected.

Below a table that summarizes the libs built for bbv1:
(ommiting the -mt- tags)
IMHO bbv2 should produce the same as a default.

  link runtime-link variant prefix tag ext
shared | shared | debug | | -gd- | dll
shared | shared | release | | | dll
static | shared | debug | lib | -gd- | lib
static | static | debug | lib | -sgd- | lib
static | shared | release | lib | | lib
static | static | release | lib | -s- | lib


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at