Re: [Boost-build] BUMPITTY BUMP: [git] genrating forward headers

Subject: Re: [Boost-build] BUMPITTY BUMP: [git] genrating forward headers
From: Bjørn Roald (bjorn_at_[hidden])
Date: 2013-09-26 02:52:49

On 09/25/2013 01:25 PM, Vladimir Prus wrote:
> On 27.08.2013 23:43, Bjørn Roald wrote:
>>
>> b2 modularized layout issue 1:
>> ------------------------------
>> build in status require build in root first, at a minimum
>> cd $BOOST_ROOT
>> b2 headers
>>
>> but default targets with just b2 seems to work as well.  I think all
>> remaining header links not used by any of the library builds get
>> created at the end.  Maybe stage target depends on headers target or
>> something, I have not checked.  Logically that would make sense.
>
> The attached patch tries to with the issue with predef, and also makes
> header targets explicit. Comments?

Patch looks good to me,

However I suspect my testing of predef is not covering the test cases 
100%, I am able to confirm that the build failure I had building predef 
/test from status folder is gone.  I tested both svn and git layouts and 
they are OK.

My concern is that I get warnings related to objective-c* on my Ubuntu 
box running ../b2 in status folder. Note that these warnings are not new 
and are not introduced by patch :

...
     - valgrind                 : yes (cached)
warn: Unable to construct ../libs/predef/test/info_as_objcpp
warn: Unable to construct ../libs/predef/test/info_as_objc
...patience...
...

I don't know much about Objective-C/C++ or how these tools are supposed 
to work in b2. In addition to default toolset (gcc) I tried clang 
toolset, but I got the same warnings.  I looked into installing gnustep, 
but it was not trivial and I don't have time to look into it.

How relevant are these warnings for verifying correctness of this patch?

The best thing is probably if someone with an Apple system can try it, 
preferably in both layouts.

-- 
Bjørn