Lines Matching refs:when
68 * Rules:: Rules describe when a file must be remade.
121 * Secondary Expansion:: How and when secondary expansion is performed.
174 * Echoing:: How to control when commands are echoed.
178 * Interrupts:: What happens when a command is interrupted.
293 * Archive Pitfalls:: Dangers to watch out for when using archives.
429 run miscellaneous commands when explicitly asked (for example, to remove
483 A "rule", then, explains how and when to remake certain files which
486 can also explain how and when to carry out an action. *Note Writing
566 specified when the target file needs to be updated.)
595 Thus, when you give the command:
665 Here is how the complete simple makefile looks when you use a
828 * Secondary Expansion:: How and when secondary expansion is performed.
840 * An "explicit rule" says when and how to remake one or more files,
846 * An "implicit rule" says when and how to remake a class of files
897 By default, when `make' looks for the makefile, it tries the following
962 One occasion for using `include' directives is when several programs,
968 Another such occasion is when you want to generate prerequisites from
1318 often a source of some confusion when writing makefiles. Here we will
1435 only becomes apparent when you discover that secondary expansions
1481 evaluate, respectively, to the file name of the target and, when the
1559 A "rule" appears in the makefile and says when and how to remake
1672 A rule tells `make' two things: when the targets are out of date,
1673 and how to update them when necessary.
1787 Wildcard expansion does not happen when you define a variable.
1851 expansion does not normally take place when a variable is set, or
2141 For example, when a file `foo.o' has no explicit rule, `make'
2159 linker. This special feature comes into play when you write a
2183 executed when `foo' is older than `foo.c' or than
2207 just a name for some commands to be executed when you make an explicit
2264 build the rest of the directories even when one fails. This can be
2288 relationship declaration is particularly important when attempting
2294 target, the phony target commands will be executed only when the phony
2378 last-modification time, when the rule's commands were last executed. It
2468 it does when it receives a signal. *Note Errors in Commands:
2503 `dst' is typically slightly older than `src' even when it is up to
2764 but it _does_ apply only when the target has no commands otherwise
2765 specified, and only when the prerequisites can be found. If more than
2796 when the same target appears in more than one rule.
2949 * Echoing:: How to control when commands are echoed.
2953 * Interrupts:: What happens when a command is interrupted.
3072 This is often the case when passing scripts to languages such as Perl,
3215 Furthermore, when you do set `SHELL' in your makefile that value is
3343 fewer jobs than when it is lightly loaded. You can use the `-l' option
3354 More precisely, when `make' goes to start up a job, and it already
3425 Usually when a command fails, if it has changed the target file at
3429 file. The situation is just the same as when the command is killed by a
3449 from scratch when `make' is next run. Why is this? Suppose you type
3456 in a strange error message from the linker when it tries to link an
3475 This technique is useful when you want separate makefiles for various
3493 `.PHONY' (for more discussion on when this is useful, see *note Phony
3496 For your convenience, when GNU `make' starts (after it has processed
3675 As a special feature, the variable `MAKELEVEL' is changed when it is
3679 sub-sub-`make', and so on. The incrementation happens when `make' sets
3764 hyphen only when it begins with an option that has no single-letter
3818 when processing is completed.
3821 it for you: `-w' is turned on automatically when you use the `-C'
3868 `foo.y' will be substituted for the variable `$^' when it occurs in
3942 Variables and functions in all parts of a makefile are expanded when
4040 distinguished in how they are defined and in what they do when expanded.
4069 will do what was intended: when `CFLAGS' is expanded in a command, it
4082 unpredictable results because you cannot easily control when they are
4091 variables and functions, when the variable is defined. The actual
4112 `MAKELEVEL', which is changed when it is passed down from level to
4374 Flavors.), though both are used together in complex ways when doing
4385 * You can specify an overriding value when you run `make'. *Note
4424 are expanded when the line is read to find the actual variable name to
4479 but differs in ways that become important when you use more complex
4484 However, when there _is_ a previous definition, exactly what `+=' does
4506 On the other hand, when you use `+=' with a variable that you defined
4508 a bit different. Recall that when you define a recursively-expanded
4512 when you refer to the new variable (*note The Two Flavors of Variables:
4525 importance of this comes when the variable's old value contains
4536 variable, meaning `$(includes) -O' is _not_ expanded when `make'
4581 For example, suppose you always want the `-g' switch when you run the
4617 when the directive is read to find the actual variable name to use.
4663 run. Every environment variable that `make' sees when it starts up is
4746 There is one more special feature of target-specific variables: when
5050 `make' evaluates conditionals when it reads a makefile.
5069 Functions.). This is useful when `touch' is not enough to make a file
5257 The function `strip' can be very useful when used in conjunction
5453 frequently means that the result will be empty when NAMES is not,
5653 You must take care when using complex variable expressions that
5690 parentheses when writing it. (You can, however, use a variable
5734 A final caution: be careful when adding whitespace to the arguments
5737 effects. It's generally safest to remove all extraneous whitespace when
5759 parentheses when writing it. (You can, however, use a variable
5799 expansion are expanded again when they are parsed as makefile syntax.
5801 characters when using `eval'. The `value' function (*note Value
5856 `$' or parentheses when writing it. (You can, however, use a variable
5943 `$' or parentheses when writing it. (You can, however, use a variable
5977 The commands run by calls to the `shell' function are run when the
6060 By giving arguments when you run `make', you can do any of these
6298 * Without the `-n' or `-q' flag, when `make' is actually executing
6335 If you have already changed the header file at a time when some files
6378 the value of a variable when you override it.)
6407 Normally, when an error happens in executing a shell command, `make'
6458 disabled when considering whether to remake makefiles (*note How
6671 is useful when `-w' is turned on automatically, but you do not
6689 undefined variable. This can be helpful when you are trying to
6703 you do not have to specify them in detail when you want to use them.
6707 the implicit rule for C compilation when it sees this combination of
6775 Of course, when you write the makefile, you know which implicit rule
6831 Not all of these rules will always be defined, even when the `-r'
6911 when `x.c', `y.c' and `z.c' all exist will execute:
6921 In more complicated cases, such as when there is no object file
7018 `-o' option to ensure that the output goes into the right file when the
7019 source file is in a different directory, as when using `VPATH' (*note
7146 Extra flags to give to the assembler (when explicitly invoked on a
7169 Extra flags to give to compilers when they are supposed to invoke
7199 made by C compilation from `N.c'; later on, when considering how to