Re: [Boost-build] feature, properties, variants, and all the rest

Subject: Re: [Boost-build] feature, properties, variants, and all the rest
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2017-08-03 19:55:19

AMDG

On 08/03/2017 01:14 PM, Stefan Seefeld via Boost-build wrote:
> On 01.08.2017 22:41, Steven Watanabe via Boost-build wrote:
>> On 08/01/2017 08:24 PM, Stefan Seefeld via Boost-build wrote:
>>> On 29.07.2017 11:24, Steven Watanabe via Boost-build wrote:
>>>> obj A : a.cpp : : <include>/a/path ;
>>>> obj B : b.cpp : [ check-target-builds A : <use>A ] ;
>>>> exe C : C.cpp : [ check-target-builds B : <use>B ]
>>>>
>>>> Now, when building C, it will go something like this:
>>>> - Building C
>>>>   - Building B from check-target-builds
>>>>     - Building A from check-target builds
>>>>       - A builds successfully
>>>> <snip>
> 
> OK, I see. Thinking this through a little, I run into some circular
> dependency, though, so I wonder how you solve this:
> The user declares target 'C'. Once it is built, it uses a "bound name"
> corresponding to the actual file being generated. However, that bound
> name can only be found in the process of building the dependency graph
> (specifically, by identifying the tool used to build it). So, how can
> you establish the "outline" of the dependency graph with 'C' being the
> final target, when it doesn't even have a name yet ?
> 

  I used indentation to indicate the sub-steps required.
"Building C" is not actually completed until the very
end.

In Christ,
Steven Watanabe