Re: [Boost-build] usage requirements for header

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-10-18 08:11:34

Gennadiy Rozental wrote:

> 
> "Gennadiy Rozental" <rogeeff_at_[hidden]> wrote in message
> news:loom.20071017T142258-881_at_post.gmane.org...
>> Vladimir Prus <ghost <at> cs.msu.su> writes:
>>
>>>
>>> On Wednesday 17 October 2007 04:31:07 Gennadiy Rozental wrote:
>>> > Can I somehow specify usage requirements for header?
>>> >
>>> > Specifically I am interrested in <toolset>msvc:<asynch-exceptions>on
>>> > for
>> all
>>> > boost/test/included headers. I see something close as an alias
>>> > minimal. I
>> am
>>> > not sure this is it and how do I use it.
>>>
>>> Can you clarify what you want? It's not possible to detect that a source
>>> file will include some header and change things based on that, and it
>>> would
>>> be in fact somewhat strange to try that.
>>
>> You know that Boost.Test requires async exceptions enabled bor msvc based
>> toolsets. For the library kind of targets we put it in project
>> requirements
>> section. But the is usage variant which doesn't involve libraries.
>> Instead user include header from boost/test/included directory, which
>> contains whole
>> source of the corresponding component. In this case async exception are
>> required as well.
>>  I do expect it to be difficult to deduce particular header usage (though
>> I
>> noticesed that bjam actually does perform header analisys to deduce
>> dependency, isn't t?), but I found alias minimal in Boost.Test Jamfile.
>> minimal is also header only component of Boost.Test. Can I do similar
>> with other headers from included directory? At best it shouldn't require
>> users to
>> include some fake dependecies in their Jamfiles, but any solution may be
>> considered.
> 
> 
> Please take a look here:
> 
> http://mysite.verizon.net/beman/win32-trunk-details.html#graph-csr_graph_test-msvc-8.0
> 
> You can see that async exceptions are not enabled. And they have to be.
> How can it be done?

If the test in question uses Boost.Test headers, but no library, and wishes
to use whatever compiler settings are recommended by Boost.Test, that 
test should include Boost.Test's 'minimal' target among its sources.

- Volodya