From: Larry Evans (cppljevans_at_[hidden])
Date: 2004-12-15 21:36:13
On 12/15/2004 04:49 PM, Larry Evans wrote:
> so the above dependency for version 1.1.3 of mpl could be expressed:
> dependency mpl
> : boost-root.ln/release/gcc/debug/libs/mpl/test.release.log.~1.1.3~
> where, there would be a versioned test.log file with entries
> as described in */msg76550.php for productions.release.log.
I realized that maybe "version 1.1.3 of mpl" doesn't make much sense.
Well what I meant was the version of all the mpl files used
to run whatever tests were in boost-root.ln/libs/mpl/test. For
example, the developer makes some changes and then runs the
tests to verify their correctness. If they pass, he decides
to create a mpl release to signify that the current version of
the mpl files pass the tests in libs/mpl/test. These mpl
files used to run the test and their versions are recorded
It would be clearer if an actual test in the directory were used.
For example, instead of test.release.log, the filename could
consist of the Jamfile and the target in the Jamfile. For instance:
Ok, the naming convention needs work, but the idea is to record
all the files and their versions used to run some program. Of
course when referencing a *.release.log file on the rhs of
a Jamfile dependency statement, the dependency should only include
files from the library, not those specific to the test (e.g.
for_each.cpp in the libs/mpl/test directory).
Please let me know if that's unclear.
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