|
|
Boost Testing : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-17 03:11:35
Hi Martin,
can you switch C++ Boost regression tests that you're running to Boost.Build
V2?
The general instructions can be found at:
https://zigzag.cs.msu.su/boost.build/wiki/BoostRegressionsV2
In your specific case, the content of user-config.jam should be:
using gcc : 3.2.3_linux : <whatever.path.to.compiler/g++ ;
using gcc : 3.3.6_linux : <whatever.path.to.compiler/g++ ;
using gcc : 3.4.5_linux : <whatever.path.to.compiler/g++ ;
using gcc : 4.0.2_linux : <whatever.path.to.compiler/g++ ;
using gcc : 4.1.0_linux : <whatever.path.to.compiler/g++ ;
using intel-linux : 9.0_linux : <whatever.path.to.compiler/g++ ;
using python : <whatever.version> : <whatever.path> ;
Speaking about python, example line is:
using python : 2.3 : C:/python ;
The command line to run the regression tests should be something like:
regression.py --v2 --toolsets=gcc-3.2.3_linux,gcc-3.3.6_linux,gcc-3.4.5_linux,gcc-4.0.2_linux,gcc-4.1.0-linux,intel-9.0_linux --runner="Martin Wille V2"
Notes:
- The --v2 option makes regression.py use Boost.Build V2
- The "-V2" suffix in runner id makes it clear that V2 is used in the
test matrix
If you want the setup for testing not to interfere with ordinary Boost.Build V2 setup,
the above configuration should be placed to file named 'test-config.jam', and that
file should be placed to a directory in BOOST_BUILD_PATH.
Also, you're testing a lot of versions, so it takes a lot of time. It might be safer if initially,
you test with only a couple of gcc versions only, in order to make turnaround in case of problems faster.
If results on two versions are fine, you can test test four gcc versions, and then will all toolsets
you test in V2.
If you have any issues or concerns or questions, please ask me right away,
either here, or via personal email, or via Jabber
(vladimir_prus_at_[hidden]), or via ICQ (100422315), or via Skype
(vladimir_prus).
Thanks in advance,
Volodya