From: Gennadiy Rozental (gennadiy_at_[hidden])
Date: 2002-09-19 02:25:41
> > boost::test_toolbox::detail::test_and_continue_impl(bool,
> > boost::test_toolbox::detail::wrapstrstream const&, char const*, int,
> > bool, boost::unit_test_framework::report_level)
> Is this part of that mandatory link strategy that was added to the new
> Test library?
More correct would be - default strategy. Right now you have 4 chooses:
1. Do not change anything in your code and link with appropriate Boost.Test
component (test_exec_monitor in majority of the cases). That what Jamfiles
are doing at the moment.
2. Use boost/test/included/test_exec_monitor.hpp instead of
boost/test/test_tool.hpp+BOOST_INCLUDE_MAIN. It may slow down your
compilation. But you won't need to link with precompiled components.
3. Use boost/test/minimal.hpp instead of
boost/test/test_tool.hpp+BOOST_INCLUDE_MAIN. It provides you with the set of
features that were defined in v1(which is most probably is want you were
using). It should not incur significant compilation slowdown and it does not
require to link with precompiled components
4. You could vote to change the default behavior of
boost/test/test_tools.hpp in case if BOOST_INCLUDE_MAIN is defined. More on
this case in the thread "Boost.Test choice"
Hope it helps,
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk