Re: [Boost-build] [RC_1_34_0] Autolinking for unit-test not workingfor GCC 4.1 x86 Linux

From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2006-11-22 17:01:27

"Dean Michael Berris" <mikhailberis_at_[hidden]> wrote in message 
news:6adba9f0611220839s57692af4xc21d4c35c6952372_at_mail.gmail.com...
> 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:
>
>  #define BOOST_AUTO_TEST_MAIN
>  #include <boost/test/auto_unit_test.hpp>
>
> To be able to avoid the BOOST_AUTO_TEST_MAIN macro in the future.

BOOST_AUTO_TEST_MAIN is deprecated, but for now this is a synonym of 
BOOST_TEST_MAIN

>> 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?

Yes. That is correct. Automatically registerred test units are natural part 
of Boost.Test now.

Gennadiy