Boost logo

Boost-Build :

From: Nicola Musatti (Nicola.Musatti_at_[hidden])
Date: 2006-12-12 17:58:59

Hallo, Robert.
I'm not exactly the top BBv2 expert around but as nobody else answered...

Robert Ramey wrote:
> in the directory .../libs/serialization/test I have a file Jamfile.v2
> which is used for testing the serialization system. I"m pretty sure
> it works as it is used for testing the library with boost 1.34
> It is common and convenient for me to run just the serialization
> library tests. In V1 I've used:
> bjam --dump-test -sTOOLS=$1 test
> which included in runtest.ksh. I would like to be able to do the
> equivalent with V2 and from reading the v2 documentation I expect the
> command to be something like:
> bjam --v2 toolset=msvc
> I've tried several variations like
> bjam --v2 toolset=msvc test bjam --v2 --dump-test toolset=msvc bjam
> --v2 --dump-test toolset=msvc test

My boost_test.bat batch file has this command:

bjam --v2 --dump-tests %*

and I call it as follows:

boost_test toolset=msvc

I *think* I specify additional toolsets separated by spaces, as in

boost_test toolset=msvc borland gcc

but in this very moment I'm not absolutely sure and I can't try it out.

> etc. But I get what to me is a cryptic message:

I don't know if it's a Borland specific problem, but I've had to
explicitly configure Python in my user-config.jam file as follows:

using python : G:/opt/Python24 ;

This is a valid path on my PC, even though this version of Python is
unusable with all of my compilers. I don't know if a fake one would do
as well.

Nicola Musatti

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