Re: [Boost-build] adding tests conditional on compiler's C++11 support

Subject: Re: [Boost-build] adding tests conditional on compiler's C++11 support
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-11-11 10:04:04

AMDG

On 11/10/2016 10:52 PM, Robert Ramey wrote:
> On 11/10/16 5:50 PM, Edward Diener wrote:
> 
>>
>> Did you add:
>>
>> import path-to-config-lib/checks/config : requires ;
>>
>> at the top of your test/jamfile.v2 where the usually correct path
>> would be:
>>
>> import ../../config/checks/config : requires ;
>>
> 
> good call.  I did go and check the Jamfile.v2 and found that it DOES
> have that statement.  I've used the "requires" facility in other tests
> and it seems to work OK.  Also, this problem is specific to darwin-4.2.1
> without the C++11 switch.  I can't help but think that this is a big
> clue to what's happening.
> 

  I'm guessing that the problem is that config.requires
directly uses the tests for Boost.Config.  The macros
are supposed to be in sync with the tests, so I think
this is a bug in Boost.Config.

In Christ,
Steven Watanabe