From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-01-05 13:02:13
At 10:53 AM 1/5/2003, David Abrahams wrote:
> To get more information from --dump-tests output,
>add <test-info>whatever to the target requirements, as many times as
>you like. If you do this, after the test name, a square-bracketed
>list of the "whatever" strings will appear in the --dump-tests output.
OK, I just tested it and it worked great.
Please don't forget the run-type though - that's the feature needed to make
subincludes work with compiler_status:
>The current output looks like:
> (boost-test "foo_test" : "libs/foo/test\foo_test.cpp" )
>If you could add the test type ("run", "compile-fail", etc.) that would
>cover the only killer requirement.
>So the above sample might become:
> (boost-test "run" "foo_test" : "libs/foo/test\foo_test.cpp" )
>That's the only "must have".
(boost-test "run" : "foo_test" : "libs/foo/test\foo_test.cpp" )
Or anything similar.
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