Subject: Re: [Boost-build] Adding "on target" variables "on the fly"
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-06-17 15:39:04
On 17.06.2017 10:24, Steven Watanabe via Boost-build wrote:
> On 06/17/2017 05:21 AM, Stefan Seefeld via Boost-build wrote:
>> Here is the use-case:
>> I'm trying to implement a config check that consists of this chain of
>> 1) determine whether the given Python version has the "numpy" module
>> installed, and if so, report the associated include path
>> 2) with that include path, try-compile a little app to make sure all
>> compiler flags work.
>> The problem (in the original bjam logic) is that all "on target"
>> variables had to be defined before the scheduler's "update" function
>> (the "update_now" rule in Jam lingua) would be called. I.e., it isn't
>> possible for one target action to add or modify variables used in
>> another, unless the two were built by separate calls to the "update_now"
> Can't you do this with __ACTION_RULE__?
True, that might be another hook to use. (In my case however, I only use
that as a one-way notification operation to let the frontend know that
an action has been completed.)
-- ...ich hab' noch einen Koffer in Berlin...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk