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

On 5/18/2015 10:57 PM, Rene Rivera wrote:

On Mon, May 18, 2015 at 9:38 PM, Rene Rivera wrote:

...

On Mon, May 18, 2015 at 8:57 PM, Edward Diener wrote:

...

On 5/15/2015 4:38 PM, Rene Rivera wrote:

...

On Fri, May 15, 2015 at 3:31 PM, Edward Diener 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.

And it's done, and checked into the predef develop branch. I need to update and regenerate docs before I can merge to master though. So things will only start working on the develop super-project.

Your change is now working correctly for me on the QNX 'develop' regression tests for VMD. The Android regression test results are started a number of days earlier than the date on the regression test itself so that it will still be a few days before I can see if your change fixes the problems running VMD 'develop' regression tests for Android.