Boost logo

Boost Testing :

Subject: Re: [Boost-testing] Running regression tests
From: Ben Pope (benpope81_at_[hidden])
Date: 2012-12-16 21:45:58

On 17/12/12 05:36, Rene Rivera wrote:
> On Sun, Dec 16, 2012 at 2:03 AM, Ben Pope <benpope81_at_[hidden]
> <mailto:benpope81_at_[hidden]>> wrote:
> Hi,
> Does anybody know how to name a toolset in a such a way that the
> summary will include line breaks? If I use "-", bjam performs some
> magic and thinks that it's a feature. I'm taking up a
> disproportionate amount of horizontal space, especially with
> clang-linux-3.2_c++11_libc++ (which should have been named without
> the linux bit, more bjam magic, I presume).
> The test results break the toolset name at the "-" characters. And you
> can shorten the name to whatever you like by giving a different name
> when setting up your compiler in he user-config.jam (or equivalent).

Yes, but if I add additional "-" to the name, bjam thinks I'm asking for
subfeatures that don't exist for that toolset.

I'd like to call my toolset: clang-3.2-c++11-libc++ (to get plenty of
line breaks), but bjam seems to tokenise the name on "-" and do clever
stuff with it, resulting in:

notice: will use 'clang++' for clang-linux, condition
in implied-subfeature from module feature
error: "3.2" is not a known subfeature value of <toolset>clang

But if I name it clang-3.2_c++11_libc++ then it works fine, but I don't
get line breaks on the results page and for some reason it adds "linux-"
to the name: clang-linux-3.2_c++11_libc++.

Would it be possible to add c++11 and libc++ as subfeatures by equating
c++11 with <cxxflags>-std=c++11 and libc++ with <cxxflags>-stdlib=libc++
in user-config.jam?

> What is required to have my test runs "promoted" to primary test
> compiler? I intend to run daily the latest release GCC and Clang
> (with libc++) on linux x86_64 with -std=c++11 for release and trunk.
> I don't understand that question.

On the history page for each release it states:
Boost's primary test compilers are:
Boost's additional test compilers include:

I was wondering how primary test compilers are chosen.



Boost-testing list run by mbergal at