[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Targets directory name concatenation strangeness
From: |
Kyle Rose |
Subject: |
Re: Targets directory name concatenation strangeness |
Date: |
Thu, 3 Aug 2017 13:08:56 -0400 |
On Thu, Aug 3, 2017 at 12:53 PM, Martin Dorey <address@hidden> wrote:
> "It’s very important that you recognize the limited scope in which automatic
> variable values are available: they only have values within the recipe. In
> particular, you cannot use them anywhere within the target list of a rule;
> they have no value there and will expand to the empty string."
As an aside, one thing I figured out a few weeks ago is that the
following *does* work as you'd hope:
%: export TARGET=$@
%: export PREREQS=$^
Combined with a replacement SHELL, this can be used to take some very
interesting implicit actions.
Kyle
- Re: Target-specific variable in subdirectory problem, (continued)
- Re: Target-specific variable in subdirectory problem, Paul Smith, 2017/08/02
- Re: Target-specific variable in subdirectory problem, Benjamin Cama, 2017/08/03
- Message not available
- Re: Target-specific variable in subdirectory problem, Benjamin Cama, 2017/08/03
- Targets directory name concatenation strangeness, Benjamin Cama, 2017/08/03
- RE: Targets directory name concatenation strangeness, Martin Dorey, 2017/08/03
- Re: Targets directory name concatenation strangeness, Benjamin Cama, 2017/08/03
- Re: Targets directory name concatenation strangeness,
Kyle Rose <=
Fwd: Re: Target-specific variable in subdirectory problem, Sven C. Dack, 2017/08/03