Re: [boost] [config] 'requires' doesn't take differing -std intoaccount

Subject: Re: [boost] [config] 'requires' doesn't take differing -std intoaccount
From: John Maddock (jz.maddock_at_[hidden])
Date: 2015-06-21 13:26:37

On 21/06/2015 17:49, Peter Dimov wrote:
>> John Maddock wrote:
>>
>> > I don't know how to address that - the requires rule just uses > 
>> Boost.Build's check_target_builds rule, so the question is why that > 
>> doesn't mangle itself on your sub-features?
>>
>> Beats me.
>
> It's probably this bit in configure.jam:
>
> rule builds ( metatarget-reference : properties * : what ? : retry ? )
> {
>    # FIXME: This should not be hardcoded. Other checks might want to 
> consider a
>    # different set of features as relevant.
>    local toolset = [ property.select <toolset> : $(properties) ] ;
>    local toolset-version-property = "<toolset-$(toolset:G=):version>" ;
>    local relevant = [ property.select <target-os> <toolset>
>        $(toolset-version-property) <address-model> <architecture> :
>        $(properties) ] ;
>
> Looking at project-cache.jam, I see that the "symlinks supported" 
> check encodes all the features. Perhaps check-target-builds should 
> just do the same?
>

+1, but we need a Boost.Build expert to check this, John.