From: John Maddock (john_at_[hidden])
Date: 2005-08-02 09:51:57
>Don't regression test build just a single variant? No debug/release
>single-threaded/multi-threaded static-runtime/dynamic-runtime combos. If
>there are no all such combos, then the testing of autolink is not so
True, but see below.
>Answering your question -- it might be possible to add BOOST_ALL_NO_LIB
Umm, what good does that do?
OK, lets see if we can design a descent testing suite, just thinking out
1) Can I have a stage target that directs the "installed" lib to a path of
2) Can I make the build of an executable depend upon a stage target being
built first? (Last time I asked for bbv1 the answer here was no).
3) I can add <runtime-link>static etc build requirements to a target, but
can I make "release" or "debug" also build requirements?
If "yes" to all of the above I think we could do something like define one
exe and one lib target for each build combination (tedious but there are
only eight of them, so it's do-able), and then all the combinations would
(hopefully) get tested?
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