On 13/11/19 5:14 pm, Sebastian Huber wrote:
> We already have a recursive substitution built in through the DAG.
Sure, and this is only a suggestion.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 12/11/2019 22:43, Chris Johns wrote:
The variables used for the substitution are the configuration set environment
variables. I intentionally didn't add a recursive substitution since you should
specify the variable definitions in a proper order.
And if there are competing orders? It all depe
On 12/11/19 5:05 pm, Sebastian Huber wrote:
> On 11/11/2019 23:29, Chris Johns wrote:
>> On 11/11/19 8:45 pm, Sebastian Huber wrote:
>>> On 08/11/2019 23:48, Chris Johns wrote:[...]
3. Is the ${} expansion something you have implemented? It is a nice
feature.
>>> [...]
>>>
>>> With stand
On 11/11/2019 23:29, Chris Johns wrote:
On 11/11/19 8:45 pm, Sebastian Huber wrote:
On 08/11/2019 23:48, Chris Johns wrote:[...]
3. Is the ${} expansion something you have implemented? It is a nice feature.
[...]
With standard Python the substitution itself is a one liner:
def substit
On 11/11/19 8:45 pm, Sebastian Huber wrote:
> On 08/11/2019 23:48, Chris Johns wrote:[...]
>> 3. Is the ${} expansion something you have implemented? It is a nice feature.
> [...]
>
> With standard Python the substitution itself is a one liner:
>
> def substitute(self, ctx, value):
>
Hello Chris,
thanks for having a look at it.
On 08/11/2019 23:48, Chris Johns wrote:[...]
3. Is the ${} expansion something you have implemented? It is a nice feature.
[...]
With standard Python the substitution itself is a one liner:
def substitute(self, ctx, value):
if isinstan
On 9/11/19 12:56 am, Sebastian Huber wrote:
> Update #3818.
> ---
>
> This is the first draft of the documentation of the new build system from the
> RTEMS maintainer perspective.
Well done. This this effort is looking nice.
> I work the documentation for the user manual next week. The next ste
