Re: [boost] [build] Tests automatically create header links, but library builds do not

Subject: Re: [boost] [build] Tests automatically create header links, but library builds do not
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2015-01-05 03:20:06

On 01/04/2015 03:58 AM, Peter Dimov wrote:
> Andrey Semashev wrote:
>> On Saturday 03 January 2015 19:00:30 Peter Dimov wrote:
>> > If I remove my boost/ directory, and attempt to build, for example, > atomic, by going into libs/atomic/build and invoking b2, it fails
>> due to > a missing header:
>> >
>> > Why is that?
>>
>> That's because Boost.Build is unable to parse #includes made with preprocessor macros. The TypeTraits headers are included from the
>> implementation headers in Atomic, which in turn are included through a macro. Boost.Build does not find those implementation headers and
>> hence do not make TypeTraits a dependency.
>
> Yes, you're right, I picked 'atomic' at random, and it turned out to be exactly the wrong choice for this kind of test. Building 'system',
> for example, works. :-)

Last time I recall you and Andrey had a discussion about the best way to handle this, and no agreement was reached?

-- 
Vladimir Prus
CodeSourcery / Mentor Embedded
http://vladimirprus.com