Re: [boost] [predef] Using predef-check on 'develop' problem

Subject: Re: [boost] [predef] Using predef-check on 'develop' problem
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2015-05-18 22:38:32

On Mon, May 18, 2015 at 8:57 PM, Edward Diener <eldiener_at_[hidden]>
wrote:

> On 5/15/2015 4:38 PM, Rene Rivera wrote:
>
>> On Fri, May 15, 2015 at 3:31 PM, Edward Diener <eldiener_at_[hidden]>
>> wrote:
>>
>>  In a jam file I have for a run test a predef-check which looks like:
>>>
>>> run test_variadic_macro.cpp : : : [ predef-check "BOOST_COMP_GNUC >= 4.3"
>>> "BOOST_OS_QNX == 0" : : <cxxflags>-std=c++0x ] ;
>>>
>>> When running on QNX with the gcc version greater than 4.3 I would expect
>>> that -std=c++0x would not be added as a C++ compile parameter to the run.
>>> Yet it is being added to the run.
>>>
>>> Another test confirms that BOOST_OS_QNX is indeed being set to a non-zero
>>> value.
>>>
>>> Is there a bug in predef-check ? Am I using it incorrectly ?
>>>
>>>
>> It looks like a bug to me.. I'll investigate further tonight.
>>
>>
> What I am also seeing, besides the QNX problem, is that for the Android OS
> 'develop' tests, using the same predef-check as above, both conditions are
> true, yet the -std=c++0x is not on the command line of the tests.

FYI.. I haven't stopped working on fixing this. And I have an almost
working resolution.

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail