Re: [Boost-build] Inheriting properties from Boost.Build testing requirements

Subject: Re: [Boost-build] Inheriting properties from Boost.Build testing requirements
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-11-13 08:29:15

On Friday 13 November 2009 14:11:48 John Maddock wrote:

> Folks,
> 
> If I modify libs/variant/test/Jamfile to contain:
> 
> project
>     : requirements
>         <toolset>msvc:<asynch-exceptions>on
>     ;
> 
> It does the right thing - which is to say it turns on asynch-exceptions for 
> msvc and all the related warning go away.
> 
> However, the "right" thing to do would be to use something like:
> 
> project
>     : requirements
>         <dependency>/boost/test//minimal
>     ;
> 
> But this results in *both* /EHsc and /EHa being passed to the compiler, with 
> the result that I see:
> 
> cl : Command line warning D9025 : overriding '/EHs' with '/EHa'
> 
> Is this a bug in the way Boost.Build is propagating dependency requirements?

John,

I am afraid this is not a bug, but known feature limitation. Only "free" properties
(like include/define) may be specified in usage requirements of the targets. Lifting
this limitation will probably require that I refresh my memory of lattice theory and
similar things, and so not something quickly hackable.

How much of a pain will it be to specify the requirements in libs/variant/test/Jamfile?
Or there are several libraries you have to modify?

- Volodya