From: David Abrahams (dave_at_[hidden])
Date: 2006-12-14 12:07:19
"Gennadiy Rozental" <gennadiy.rozental_at_[hidden]> writes:
> "David Abrahams" <dave_at_[hidden]> wrote in message
>> "Gennadiy Rozental" <gennadiy.rozental_at_[hidden]> writes:
>>> "David Abrahams" <dave_at_[hidden]> wrote in message
>>>> You can review the guide at
>>>>> 4. The only Boost libraries that can't be used without separate
>>>>> compilation are
>> Thanks for looking at this, Gennadiy,
>>> This is not exactly true for Boost.Test. Boost.Test supplies inline
>>> versions for all components. This need to be somehow reflected to
>>> avoid confusion.
>> So Boost.Test *doesn't* require separate compilation?
>> If that's the case, I'll remove it from the list and add a mention of
>> it to the paragraph at the bottom of the box
> Well. As usual the picture is gray :o)
> The statement "Boost.Test can't be used without separate compilation" is
> incorrect: all Boost.Test component have inline verstion
Which is the default? If I just compile against the Boost.Test
headers will it work, or do I need to set some #define?
I need to know so I can tell people what they have to do.
> 1. Some (most?) boost libraries *will* require offline library for their
> unit tests to work
Are you just saying that if you want to test Boost, you'll need the
separate Boost.Test binary? I don't see why that would matter one bit
to the reader, since it's built automatically and on demand by the
build system when you run the tests.
> 2. It's not required but recommended to precompile at least UTF
I need to know so I can tell people why they should care.
>> I'm very concerned about adding needless complication to this
>> introductory document. Maybe in the section 8 that would be an
>> appropriate place for links to library-specific build/configuration
> Summary of Boost.Test build instructions should be located here
> libs/test/doc/compilation.html I will try to put it there soon
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk