Lines Matching full:automatic
170 * Automatic Prerequisites:: How to automatically generate rules giving
307 * Automatic Variables:: How to use automatic variables in the
1132 @code{make}. @xref{Automatic Prerequisites}.
1133 @cindex prerequisites, automatic generation
1134 @cindex automatic generation of prerequisites
1579 and @code{ifneq} forms. Of course this means that automatic variables
1580 cannot be used in conditional statements, as automatic variables are
1582 need to use automatic variables in a conditional you @emph{must} use
1672 always take place within the scope of the automatic variables for that
1711 Evaluation of automatic variables during the secondary expansion
1716 The subtleties of using the different automatic variables are
1771 target pattern. The value of the automatic variables is derived in
1856 * Automatic Prerequisites:: How to automatically generate rules giving
2082 Targets, ,Empty Target Files to Record Events}. (The automatic variable
2084 @ref{Automatic Variables}.)@refill
2477 This is done with the @dfn{automatic variables} such as @samp{$^}
2478 (@pxref{Automatic Variables}).
2496 want to mention in the commands. The automatic variable @samp{$<} is
2526 The commands of implicit rules normally use automatic variables as a
2822 automatic variable @samp{$?} is used to print only those files that have
2823 changed (@pxref{Automatic Variables}).
3043 to be absolutely identical, since the automatic variable @samp{$@@}
3045 commands (@pxref{Automatic Variables}). For example:
3231 Here @samp{$<} is the automatic variable that holds the name of the
3232 prerequisite and @samp{$@@} is the automatic variable that holds the name
3233 of the target; see @ref{Automatic Variables}.
3310 @node Double-Colon, Automatic Prerequisites, Static Pattern, Rules
3346 @node Automatic Prerequisites, , Double-Colon, Rules
3348 @cindex prerequisites, automatic generation
3349 @cindex automatic generation of prerequisites
3407 The practice we recommend for automatic prerequisite generation is to have
4812 just a few characters. These are the @dfn{automatic variables}, and
4813 they have particular specialized uses. @xref{Automatic Variables}.
4882 the case of the automatic variables (@pxref{Automatic Variables}).
5363 Several @dfn{automatic} variables are given new values for each rule.
5365 @xref{Automatic Variables}.
5413 @dfn{automatic} variables (@pxref{Automatic Variables}).
5750 course). One exception to that is automatic variables
5751 (@pxref{Automatic Variables}).
5756 automatic variables, these values are only available within the context
6142 Consequently, you cannot use automatic variables in the tests of
6144 (@pxref{Automatic Variables}).
7204 @item automatic
7206 if @var{variable} is an automatic variable defined for the
7208 (@pxref{Automatic Variables}).
7504 during @code{clean} rules (@pxref{Automatic Prerequisites}), so
8915 You can prevent automatic deletion of an intermediate file by marking it
8970 * Automatic Variables:: How to use automatic variables in the
9049 @node Pattern Examples, Automatic Variables, Pattern Intro, Pattern Rules
9063 @file{@var{x}.c}. The command uses the automatic variables @samp{$@@} and
9065 in each case where the rule applies (@pxref{Automatic Variables}).@refill
9106 @node Automatic Variables, Pattern Match, Pattern Examples, Pattern Rules
9107 @subsection Automatic Variables
9108 @cindex automatic variables
9109 @cindex variables, automatic
9117 What you do is use a special feature of @code{make}, the @dfn{automatic
9123 @cindex automatic variables in prerequisites
9124 @cindex prerequisites, and automatic variables
9126 automatic variable values are available: they only have values within
9134 automatic variable values to be used in prerequisite lists.
9136 Here is a table of automatic variables:
9140 @vindex @@ @r{(automatic variable)}
9149 @vindex % @r{(automatic variable)}
9157 @vindex < @r{(automatic variable)}
9164 @vindex ? @r{(automatic variable)}
9173 @vindex ^ @r{(automatic variable)}
9187 @vindex + @r{(automatic variable)}
9195 @vindex | @r{(automatic variable)}
9201 @vindex * @r{(automatic variable)}
9250 @vindex @@D @r{(automatic variable)}
9258 @vindex @@F @r{(automatic variable)}
9265 @vindex *D @r{(automatic variable)}
9268 @vindex *F @r{(automatic variable)}
9274 @vindex %D @r{(automatic variable)}
9277 @vindex %F @r{(automatic variable)}
9286 @vindex <D @r{(automatic variable)}
9289 @vindex <F @r{(automatic variable)}
9295 @vindex ^D @r{(automatic variable)}
9298 @vindex ^F @r{(automatic variable)}
9304 @vindex +D @r{(automatic variable)}
9307 @vindex +F @r{(automatic variable)}
9314 @vindex ?D @r{(automatic variable)}
9317 @vindex ?F @r{(automatic variable)}
9324 automatic variables; we write ``the value of @samp{$<}'', rather than
9332 @node Pattern Match, Match-Anything Rules, Automatic Variables, Pattern Rules
9709 When the commands of a pattern rule are executed for @var{t}, the automatic
9711 @xref{Automatic Variables}.
9813 Implicit rules such as this one are written using the automatic variable
9814 @samp{$%}. @xref{Automatic Variables}.
9819 automatic updating with this command:
9827 named @file{file.o}. In connection with such usage, the automatic variables
9976 The automatic variable @code{$%} is set to the member name
9977 in an archive reference. @xref{Automatic Variables}.
9980 The automatic variables @code{$@@}, @code{$*}, @code{$<}, @code{$%},
9983 extension. @xref{Automatic Variables}.@refill
10033 The automatic variable @code{$^} containing a list of all prerequisites
10035 did. @xref{Automatic Variables}. The automatic variable
10229 strings. We feel it is much cleaner to always use automatic variables
10233 In some Unix @code{make}s, the automatic variable @code{$*} appearing in
10238 @vindex * @r{(automatic variable), unsupported bizarre usage}
10525 Here is a summary of the automatic variables.
10526 @xref{Automatic Variables},
