Lines Matching refs:definition

957 @cindex rule, explicit, definition of
958 @cindex explicit rule, definition of
966 @cindex rule, implicit, definition of
967 @cindex implicit rule, definition of
974 @cindex variable definition
976 A @dfn{variable definition} is a line that specifies a text string
978 simple makefile example shows a variable definition for @code{objects}
1018 definition of the variable, but rather kept intact in the value of the
3531 has been started until another rule or variable definition) will be
3551 A variable definition in a ``rule context'' which is indented by a tab
3553 not a @code{make} variable definition, and passed to the shell.
4247 definition of @samp{-t}, a @samp{make -t} command in the example would
4661 @code{endef} marks the end of the definition; the lines in between are the
4946 referenced in the definition will be executed every time the variable is
5055 (Imagine something like @w{@samp{$(dir)/file}} with this definition!)
5356 verbatim definition (@pxref{Defining, ,Defining Variables Verbatim}).@refill
5395 the definition is made.  @xref{Flavors, ,The Two Flavors of Variables}.
5401 amount of swapping space on the computer.  When a variable definition is
5403 backslash-newline at convenient places in the definition.  This will not
5470 variable.  However, when there @emph{is} a previous definition, exactly
5477 definition of the variable.  If you defined it first with @samp{:=},
5479 simply-expanded definition, and expands the new text before appending it
5541 Using @samp{=} for the definition makes @code{CFLAGS} a recursively-expanded
5543 @code{make} processes the definition of @code{CFLAGS}.  Thus, @code{includes}
5557 -pg}}, and a later definition of @code{includes} will have no effect.
5631 @cindex verbatim variable definition
7040 definition; in that case the @code{value} function will return the
7108 definition (in @code{PROGRAM_template}) could need to be much more
7175 if @var{variable} has a default definition, as is usual with @code{CC}
7178 function will return the origin of the later definition.
7216 a definition of @code{bletch}.  However, if @file{foo} defined
7218 definition.  This could be done by using an @code{override} directive in
7219 @file{foo}, giving that definition precedence over the later definition in
7238 If you want to override a previous definition of @code{bletch} if it came
7493 parsed as a switch or variable definition, respectively).  Even
10237 this; it is utterly inconsistent with the normal definition of @code{$*}.
10345 Define a variable, overriding any previous definition, even one from