From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-08-05 12:16:51
At 02:01 AM 8/5/2003, Rene Rivera wrote:
>>* We need to test this build process on a daily basis. I don't know
>>if that means adding to the current regression tests or adding a
>>separate test framework.
>IMO adding a separate framework is easier than trying to integrate to the
>current one. We would not want to break the regression testing, given
>it's working nicely. And testing the build is considerably easier.
>Initially just making a build script, ala tools/regression/run_tests.sh,
>that automates the fetch/build/process. And like the regression parse the
>log for errors. etc.
>Is process_jam_log flexible enough to parse the output of a regular
>I could write a quick Perl script, otherwise.
I'd rather wait a bit until the requirements become clearer. The point for
now is to just start thinking about the idea that not only must this
build/install procedure work, but we also need to test regularly to make
sure it stays working.
>>* The include directory and its sub-directories are getting built, and
>>have files with what appears to be the correct names. The contents of
>>the files are all identical, and are not at all correct.
>Hmm, doesn't happen to me. Just tried it with all the latest code and
>and it copied files correctly. What build command did you use?
cd \boost // parent directory
md build_test // target directory
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