From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-04-13 04:31:39
Martin Wille wrote:
> David Abrahams wrote:
>> What is going on with Boost.Build version 2? Are we going to go
>> through _another_ release cycle without retiring version 1? I think
>> the upgrade to version 2 had better be a requirement for this
>> release. That may upset people not too involved with the development
>> of the build system, but having our attention spread across three
>> versions (yes, three -- there's a Python port underway) is costing
>> Boost too much. Getting our build/test system to be solid is crucial
>> for Boost as a whole and that isn't going to happen until the BB team
>> regains its focus.
> If it would be of any help and if it actually can be done with the
> current states of BBv2 and the test system then I could set up a Linux
> box with BBv2 based Boost regression testing for some weeks. The box
> would be able to produce more than one result set per day for a single
> Aleksey/Misha: does regression.py support BBv2 or could support for BBv2
> be added within reasonable time?
I think so. Today I've committed the changes that add --v2 option to the
process_jam_log command. Just adding that should do the trick.
Is there any way to run regression.py without uploading the logs, so that I
Right at the moment I'm tracking down the remaining differences between V1
and V2 test results on Linux. Once that done -- hopefully in a day or two
-- it would be really great if you could run tests with V2 to verify that
my system is not the only one where V2 works OK.
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