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-10-29 17:09:17

On 29.10.2016 16:50, Steven Watanabe wrote:
>> * 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)
> }

I see. So '>' and '<' are pre-defined variables ? Are there other
predefined variables beside those ?
(Where in the code does the expansion happen ?)

>
> LIBRARIES = <pbin>lib.a ;
> SEARCH on <pbin>lib.a = ./bin ;
>
> Then in the body of link, $(LIBRARIES) will
> expand to ./bin/lib.a.
>
> The int is the flags defined here:
> https://github.com/boostorg/build/blob/develop/src/engine/rules.h#L54
>
>> * Is there a way to control the output, i.e. filter whatever output
>> actions generate (for example to colour it, as per a recent suggestion
>> from the list) ?
>>
> You can only adjust whether there is output or not.
> (The quietly flag suppresses output for an action)
> Anything further requires changes to the C implementation.

Thanks,
        Stefan

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