From: Benjamin Kosnik (bkoz_at_[hidden])
Date: 2007-01-19 11:44:14
>> In addition, I'm more interested in checking my local build, after I
>> built it, not really the workflow envisioned from this script. (As
> In this case you might be better off going to boost_root/status and
> issue "bjam toolset=<my-toolset>" from there. Probably it also is a good
> idea to capture the output to a file for later review.
Ooop. Sorry, this is what I'd meant by running bjam in the status directory.
As you say, it's a good idea to capture the output. However, it's 13M: I
need something more concise.
So, my original issue remains: how to get the summary?
In boost v1, using run_tests.sh I got something that could be eyeballed.
So, from that, I'm assuming something like:
bjam $bjam_flags | >& regress.log
cat regress.log | process_jam_log
then some kind of invocation of compiler_status.
However, I cannot figure out which directory compiler_status is to be
run in: it seems to be particular, and want a "Jamfile". But, which one?
The v1 build log shows directories that don't exist in v2.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk