"David Abrahams" <dave@boost-consulting.com> wrote in message news:87ejr28kzc.fsf@pereiro.luannocracy.com...
"Gennadiy Rozental" <gennadiy.rozental@thomson.com> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:87slfltf8p.fsf@pereiro.luannocracy.com...
"Gennadiy Rozental" <gennadiy.rozental@thomson.com> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:87lkleyww8.fsf@pereiro.luannocracy.com...
You can review the guide at http://www.boost-consulting.com/boost/more/getting_started.html.
4. The only Boost libraries that can't be used without separate compilation are ... Boost.Test
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?
There is no default. You could use either of them. It all depends on what header you are including Test module with #include <boost/test/unit_test.hpp> Will need an offline library The same test module but with #include <boost/test/included/unit_test.hpp> won't need an offline library.
I need to know so I can tell people what they have to do.
But:
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.
I don't share yet your optimism on expecting all Boost users to learn and use Boost.Build system. But you may have a point here.
2. It's not required but recommended to precompile at least UTF
Why?
The UTF is comparatively heavyweight component. Would you prefer Boost.Python users to include all your sources into their project and compile them every time? That's why I say it's preferable in a long term to build standalone library. I do provide an "included" option, but mostly as a helper for the "very hurry" users. Gennadiy