[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Evaluating a variable only once after a recipe has run
From: |
Paul Smith |
Subject: |
Re: Evaluating a variable only once after a recipe has run |
Date: |
Sat, 18 Apr 2020 14:43:24 -0400 |
On Sat, 2020-04-18 at 19:34 +0200, R. Diez wrote:
> > > You may find this trick from my blog to be helpful: > >> >
> > http://make.mad-scientist.net/deferred-simple-variable-expansion/
>
> Would it be possible to encapsulate it somehow, so that other people
> immediately know what is going on?
I don't see why not. Do you think there is some reason it wouldn't be
possible?
- Evaluating a variable only once after a recipe has run, R. Diez, 2020/04/18
- Re: Evaluating a variable only once after a recipe has run, Kaz Kylheku (gmake), 2020/04/18
- Re: Evaluating a variable only once after a recipe has run, R. Diez, 2020/04/18
- Re: Evaluating a variable only once after a recipe has run, Kaz Kylheku (gmake), 2020/04/18
- Re: Evaluating a variable only once after a recipe has run, R. Diez, 2020/04/18
- Re: Evaluating a variable only once after a recipe has run, R. Diez, 2020/04/18
- Re: Evaluating a variable only once after a recipe has run,
Paul Smith <=
- Re: Evaluating a variable only once after a recipe has run, R. Diez, 2020/04/18
- Re: Evaluating a variable only once after a recipe has run, Paul Smith, 2020/04/18
Re: Evaluating a variable only once after a recipe has run, Paul Smith, 2020/04/18