8 Apr
2022
8 Apr
'22
3:09 p.m.
On 4/7/22 2:05 PM, Tom Rini wrote:
On Fri, Nov 19, 2021 at 12:36:46PM +0800, Artem Lapkin wrote:
Add possibility setup env variable with additional resolving vars inside
value.
Usage examples:
=> setenv a hello; setenv b world; setenv c '${a} ${b}' => setenv -r d '${c}! ${a}...' => printenv d d=hello world! hello...
/* internal usage example */ env_resolve("d", "${c}! ${a}..."); /* d="hello world! hello..." */
Signed-off-by: Artem Lapkin art@khadas.com Reviewed-by: Simon Glass sjg@chromium.org
This break building on a number of platforms such as am335x_evm.
Should this even be applied in the first place? I agree with Wolfgang's objections. This should be done by the shell (if anything).
--Sean