usage requirements for header

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.

Gennadiy 



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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.

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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.

Gennadiy


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

"Gennadiy Rozental" <rogeeffgmail.com> wrote in message 
news:loom.20071017T142258-881post.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?

Gennadiy 



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Gennadiy Rozental wrote:

> 
> "Gennadiy Rozental" <rogeeffgmail.com> wrote in message
> news:loom.20071017T142258-881post.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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

"Vladimir Prus" <ghostcs.msu.su> wrote in
message 
news:ff7ihm$pnn$1ger.gmane.org...
> Gennadiy Rozental wrote:
>
>>
>> "Gennadiy Rozental" <rogeeffgmail.com> wrote in message
>> news:loom.20071017T142258-881post.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.

But this test most probably has nothing to do with minimal
testing 
framework. What I am looking for is similat targets for
other "inlined" 
Boost.Test components.

Gennadiy 



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Gennadiy Rozental wrote:

>>> 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.
> 
> But this test most probably has nothing to do with
minimal testing
> framework. What I am looking for is similat targets for
other "inlined"
> Boost.Test components.

Well, the test you've pointed me at seem to include
<boost/test/minimal.hpp>
so for this test, it's quite appropriate.

Other than that, you can either rename 'minimal' to
'headers' or copy-paste
'minimal' into headers, and they add /boost/test//headers to
sources
of test tests.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build