From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-01-13 02:16:39
David Abrahams wrote:
> Happy New Year, everyone!
Happy New Year!
> It's a brand new year; Boost should switch to a "brand new" build
> system, ASAP. How close are we to being able to make that switch?
Good question. The absolutely fair answer is that we don't know until we
try. I can get the ball rolling, but we really need to decide on the steps
to be made, and work on them together to push this to completion. Here are
the steps that I'd propose:
1. I set up a script that will run all Boost regressions with V1 and V2 and
compare results, and adjust V2 Jamfiles to get zero differences on
2. Somebody else with Linux/gcc run the same script to verify the results
are the same for him too.
3. Somebody with Windows/msvc compares V1 and V2 results too, coordinating
with me to get them equal.
4. We adjust the regression.py script to have "--v2" switch and ask some of
the current regression runners to test it.
5. We post to Boost mailing list, explaining that we're technically ready to
move to V2, and if anybody has any arguments against.
6. Regression runners switch to V2 and "bjam" in Boost starts to use V2 by
default, with V1 invoked by "--v1" option.
7. Any issues are ironed out.
There are two issues that are likely to arise along the way:
1. I still haven't tried to port serialization tests to V2, and they are
2. The auto-configuration of toolsets works with msvc only, so we need to
add auto-configuration to gcc, at least.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk