Re: [Boost-build] prototyping alternative Boost.Build syntax

Subject: Re: [Boost-build] prototyping alternative Boost.Build syntax
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-11-04 09:29:07

On 03.11.2016 11:20, Steven Watanabe wrote:

>>> <snip>
>>>   on TARGET variables (such as SEARCH) can
>>> be set using set-target-variable, defined
>>> in kernel/bootstrap.jam.
>> Again, I'm actually looking for the C API equivalent of these (given
>> that I'm interfacing with the engine using Python rather than Jam).
>>
> It's stored in the settings member of TARGET.

OK, thanks.

I have done some work on my Python port, and am now able to set
target-specific variables and use them (example:
https://github.com/stefanseefeld/boost.build/blob/proto/example/action/build.py#L17)

I previously added support for Python callables as actions (use the
existing "function_python" function
(https://github.com/stefanseefeld/boost.build/blob/proto/src/engine/function.c#L4998).
However, calling that won't see these target-specific variables yet. I'm
not exactly sure what is missing for this to work (something to do with
"pushsettings()", I suppose).

Thus I have a few questions:

* where in the code are target settings activated / deactivated so they
are visible to actions ?
* what is a "module" and how is it used in the engine ?

Thanks,
        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...