From: Robert Ramey (ramey_at_[hidden])
Date: 2003-10-19 15:16:43
I've recently updated my CVS tree for the development version of
boost and found the following differences when I try to build
and run tests from with in a current test directory
a) The test executables are built in
b) process_jam_log seems to work as one would
expect on the new directory
c) I can't generate compiler status tables for one test
$ compiler_status --compiler vc7 c:/boost-dev/ compiler_status.html
**** exception(205): std::exception: boost::filesystem::directory_iterator const
ructor: "c:\boost-dev\libs\serialization\test\bin": The system cannot find the p
******** errors detected; see standard output for details ********
suggesting that this program hasn't be updated to reflect a change
in expected directory structure.
among trying different options I get
what is the recommended way to build and run tests for one library?
While we're on the subject of compiler_status program, I would much like
to see a switch added "--target=<target name>" so that I could run
the tests built in release mode. Perhaps other switches as well. This
would permit me to run tests in release mode with varying combinations
of libraries and maintain one table.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk