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-03 10:38:37

On 29.10.2016 16:50, Steven Watanabe wrote:
>
>> * can a target be something other than a file, perhaps with no
>> filesystem representation at all ?
>>
> Yes.  NOTFILE marks a target as not
> referring to a real file.

In what way does bjam/b2 handle NOTFILE targets differently from other
targets ? And what other target types (or attributes) exist ?
How can I instantiate / declare targets using these non-default
attributes using the bjam Python API (or the C API, if there isn't any
Python binding for it yet) ?
>
>> * The bjam.define_action() function takes a list and an int as third and
>> fourth argument. What are these used for ?
>>
>   The list is a list of variable names.
> The variable names should be a list of
> targets which will be translated from
> the target name to the filesystem path.
>
> Example:
>
> actions link bind LIBRARIES {
>   g++ $(>) -o $(<) $(LIBRARIES)
> }
>
> LIBRARIES = <pbin>lib.a ;
> SEARCH on <pbin>lib.a = ./bin ;
>
> Then in the body of link, $(LIBRARIES) will
> expand to ./bin/lib.a.

Again, in the C (or Python) API, where are these variables defined so
that they can be properly substituted if requested by the

bjam.define_action() call ?

Thanks,
        Stefan

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