Boost logo

Boost-Build :

From: Aleksey Gurtovoy (alexy_at_[hidden])
Date: 2005-06-13 17:34:00

David Abrahams writes:
> Aleksey Gurtovoy <alexy_at_[hidden]> writes:
>> I've finally had a look at Digital Mars' link failures
>> (e.g. and after a quick research realized
>> that these are simply due to the fact that by default our tests
>> require dynamic linking, and the Digital Mars distribution available
>> for online download (as opposite to the CD-ROM distribution) does not
>> contain necessary library files.
>> [Walter, is there any chance we could get these without cashing out
>> $42.50 for the CD (for testing purposes only, of course)?]
>> We could resolve this in the short term by changing the default
>> <runtime-link> settings for the Digital Mars toolset to "static", but
>> I'm not sure whether it's possible on the toolset level. Is it? Or do
>> the DMC tests have to be run in a separate batch?
> It's easy enough to integrate the addition of
> as a requirement into the testing rules. Probably we really need
> something like
> where dmc-compilers is a list of the names of DMC toolsets being
> used.

OK. Can we have it, please? :) [Assuming that "it", which was
stripped, would be an equivalent of passing "<runtime-link>static" to
bjam command line].

> I imagine that what we want is toolsets beginning with "dmc-"
> and not containing "stlport?"

Actually it's C runtime that is missing from the online distribution,
so STLPort runs are affected as well. How about we switch the tests to
static linking when the toolset name ends with "-static"? That would
be more general and allow us to switch back to dynamic linking (or run
two set of tests in parallel) when we get the CD generously offered by

Aleksey Gurtovoy
MetaCommunications Engineering

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