Re: [Boost-build] The future of B2?

Subject: Re: [Boost-build] The future of B2?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-10-13 11:38:15

AMDG

On 10/13/2016 08:03 AM, Rene Rivera wrote:
> On Tue, Oct 4, 2016 at 11:30 AM, Klemens Morgenstern <
> klemens.morgenstern_at_[hidden]
> <javascript:_e(%7B%7D,'cvml','klemens.morgenstern_at_[hidden]');>> wrote:
> 
> (5) Post-build scanners
>>
>> Afaik boost.build provides scanners for things like include files etc. to
>> generate dependencies. I'd like to have post-build scanners, which could be
>> used to check additional generated files. E.g. when building java you have
>> additional .class files for each nested class. It would be nice if they
>> could be also collected, so I'd have them not only as dependency but as
>> part of the target, e.g. when I'd want to build a jar.
>>
>> This would also require to declare "incomplete targets", i.e. a target
>> where I don't know exactly what is the result.
>>
> 
> I understand.. But this is not an easy feature to implement. As it
> essentially means a mutating build graph while one is building. But it
> could be done with some restrictions.
> 

  At the Jam level, the build graph already
does get mutated somewhat, since #include scanners
can run on built targets (and, yes, getting it
to work correctly was quite a pain).  This particular
scenario can actually be simulated by having
the compile rule emit an auxiliary file that
lists the extra outputs and letting the jar
rule consume this list.

In Christ,
Steven Watanabe