Boost logo

Boost-Build :

From: Dean Michael Berris (mikhailberis_at_[hidden])
Date: 2006-11-22 11:39:17

Hi Juergen!

On 11/22/06, Juergen Hunold <hunold_at_[hidden]> wrote:
> On Wednesday 22 November 2006 15:05, Dean Michael Berris wrote:
> >
> > I already have `#define BOOST_AUTO_TEST_MAIN ` just before including
> > the Boost.Test header -- this I think is a remnant of Boost 1.33.1's
> > requirements. Is this a deprecation of the BOOST_AUTO_TEST_MAIN
> > macro, or is this a bug in Boost.Test or Boost.Build?
> That depends :-))
> Well, the documentation is not up-to-date, so I think the best way is to
> consider BOOST_AUTO_TEST_MAIN as deprecated.

Okay, I should try migrating the old test code that relied on:

  #include <boost/test/auto_unit_test.hpp>

To be able to avoid the BOOST_AUTO_TEST_MAIN macro in the future.

> At least
> > // Setup Boost Auto-Testing
> > #define BOOST_TEST_MAIN
> > #include <boost/test/unit_test.hpp>
> works just fine for me. ;-))
> The question _how_ to handle the platform specific issues (Win32 mostly)
> is going on right now. The best solution is to link statically when not
> using BOOST_AUTO_TEST at the moment.

So in 1.34, I shouldn't have to worry about using
<boost/test/auto_unit_test.hpp> for auto-unit tests, and just use
<boost/test/unit_test.hpp> instead?

In my case the linking doesn't bother me too much -- the code is still
being built with 1.33.1 anyway, I'm just experimenting with building
it with RC_1_34_0 and the new boost-build system. At any rate, I'm
trying to make changes to the build files that will satisfy both 1.34
and 1.33 and so far it's working out pretty well (considering that
1.33's bbv2 implementation is pretty crippled compared to the latest
in RC1.34).

Thanks for the tips!

Dean Michael C. Berris
C++ Software Architect
Orange and Bronze Software Labs, Ltd. Co.
email: dean_at_[hidden]
mobile: +63 928 7291459
phone: +63 2 8943415
other: +1 408 4049532

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at