From: David Abrahams (dave_at_[hidden])
Date: 2003-02-01 16:57:58
Beman Dawes <bdawes_at_[hidden]> writes:
> Even the briefest of documentation would be a big help for new users.
> It would be great if someone could contribute a page about using
> testing.jam. Wouldn't need to be reference quality documentation -
> just a description of how to accomplish common tasks would be very
I agree, but I don't have the perspective to know what the common
tasks are. If you'd like to take a stab at it I could correct errors
and fill in details.
> >That's because, for whatever reason, John chose to ignore the
> >input-files argument and sick the test files into the unparsed
> >command-line arguments. In doing so, he gives up important
> >advantages, including the ability to specify the input files with a
> >path relative to the Jamfile directory, and most importantly, a build
> >dependency that causes the tests to be re-run when the input files
> >have changed.
> He may have not realized that was the impact.
Maybe not. It looks like it was probably my fault for not updating
the tests in status/Jamfile when I added the input-files feature.
> With the Python tests, aren't there a few tool-chain dependencies?
> I think we are going to need to be able to turn off certain tests from the
> command like, so that people who don't have Python installed could still
> run the rest of the tests.
It's easy enough to automatically avoid running them if Python isn't
present or properly configured.
-- David Abrahams dave_at_[hidden] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
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