Re: [Boost-build] Failing dependency_test.py test.

Subject: Re: [Boost-build] Failing dependency_test.py test.
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-07-16 11:04:10

AMDG

On 07/16/2012 06:36 AM, Jurko Gospodnetić wrote:
>   Hi.
> 
>>> The problem is a result of these dependencies:
>>>
>>> INCLUDES x.cpp : x.bar ;
>>> DEPENDS <object(c-scanner)>x.cpp : x.cpp ;
>>>
>>> The result is that <object(c-scanner)>x.cpp
>>> (which binds to x.cpp) depends on x.bar.
>>
>>    Ok, what if we could avoid the INCLUDES x.cpp : x.bar all together?
>>
>>    I found that the include in question is added in virtual-target.jam
>> in the action.actualize() rule where all targets are said to include
>> each other. There is also the following comment above this code:
>>
>> <snip>
>>
>>    If we updated Boost Jam to work correctly in this case there would be
>> no more need for this INCLUDE, right?
> 
>   Nah, no luck. That bug, if it ever existed, has since been fixed in
> Boost Jam. I've tested it using the following test and it passes every
> time:
> 

That's because Boost.Jam fixes the
problem in the same way--by adding INCLUDES.

In Christ,
Steven Watanabe