From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-04-08 10:22:16
the new test system is committed to CVS, along with documentation. See
A couple ot example is at:
Just unpack that zip to tools/build/test and run test1.py, and then
test2.py... after reading till the end of this message.
The only big problem is that path to bjam is hardcoded in BoostBuild.py, so
you'd need to change it manually. Before fixing it, let's decide what we
want. Will it be ok to just run whatever "bjam" happens to be in path? Or we
should run the version in the current working copy? The latter seems better.
Also please note that matching jam output is complicated by the fact that jam
adds trailing whitespaces. We'll need to do something about it, e.g. fixing
David, I've did nothing about your refactoring suggestions. So far, I'm not
yet convinced that we'll have big advantages, and since test system is needed
now, let's go on with what we have.
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