Lines Matching refs:commands
8 and issues the commands to recompile them.
42 and issues the commands to recompile them.
131 * Force Targets:: You can use a target without commands
161 * Commands/Search:: How to write shell commands that work together
174 * Echoing:: How to control when commands are echoed.
175 * Execution:: How commands are executed.
176 * Parallel:: How commands can be executed in parallel.
180 * Sequences:: Defining canned sequences of commands.
181 * Empty Commands:: Defining useful, do-nothing commands.
186 * Variables in Commands:: Using `make' variables in commands.
191 to run commands.
199 helps debug use of recursive `make' commands.
253 kind of thing to do with the commands
266 to get the commands for updating a file.
271 * Last Resort:: How to define commands for rules which
282 commands of implicit rules.
308 program need to be recompiled, and issues commands to recompile them.
336 and provides commands for updating each file. In a program, typically,
348 those files, it issues the commands recorded in the data base.
396 your commands: you can almost always emulate what such a tool would do
397 with simple shell commands. Finally, be sure to explain what you
429 run miscellaneous commands when explicitly asked (for example, to remove
479 rule that specifies commands for the target need not have
485 commands on the prerequisites to create or update the target. A rule
505 defining editing commands include `command.h', and only low level files
560 prerequisites. These shell commands say how to update the target file.
563 mind that `make' does not know anything about how the commands work.
564 It is up to you to supply commands that will update the target file
565 properly. All `make' does is execute the commands in the rule you have
574 commands. Targets that do not refer to files but are just actions are
698 It is not necessary to spell out the commands for compiling the
703 can therefore omit the commands from the rules for the object files.
708 the `.c' files from the prerequisites, provided we omit the commands.
843 may also give commands to use to create or update the targets.
848 file with a name similar to the target and gives commands to
1208 commands but no prerequisites, that file will always be remade (*note
1210 double-colon rule with commands but no prerequisites will be remade
1215 which are specified as targets of a double-colon rule with commands but
1241 it in, and then print the commands to update `foo' and its prerequisites
1242 without running them. The commands printed for `foo' will be those
1252 print the commands needed to update it without actually running them,
1253 and then print the commands needed to update `foo' without running
1254 them. The commands for `foo' will be those specified by the existing
1266 However, if the two makefiles give different commands for the same
1289 `GNUmakefile', so it will use the commands from the pattern rule: `make
1296 prerequisite `force', to guarantee that the commands will be run even
1298 commands to prevent `make' from searching for an implicit rule to build
1370 immediately, and the commands used to construct the target are always
1562 target, and "commands" to use to create or update the target.
1587 * Force Targets:: You can use a target without commands
1699 commands: any commands necessary to build any of a target's
1700 prerequisites will be fully executed before any commands necessary to
1746 and in prerequisites. In commands the shell is responsible for
1767 Wildcards can be used in the commands of a rule, where they are expanded
1911 * Commands/Search:: How to write shell commands that work together
2104 search, this cannot change the commands of the rule; they will execute
2105 as written. Therefore, you must write the commands with care so that
2124 not want to mention in the commands. The automatic variable `$<' is
2148 The commands of implicit rules normally use automatic variables as a
2207 just a name for some commands to be executed when you make an explicit
2211 If you write a rule whose commands will not create the target file,
2212 the commands will be executed every time the target comes up for
2225 commands would not be executed. To avoid this problem, you can
2232 Once this is done, `make clean' will run the commands regardless of
2265 overcome by adding shell commands to note the error and exit, but then
2292 if it is, its commands are run every time `make' goes to update that
2294 target, the phony target commands will be executed only when the phony
2343 If a rule has no prerequisites or commands, and the target of the rule
2346 depending on this one will always have their commands run.
2355 target `clean' that depends on it is forced to run its commands. There
2373 commands for an action that you request explicitly from time to time.
2378 last-modification time, when the rule's commands were last executed. It
2379 does so because one of the commands is a `touch' command to update the
2384 commands are executed if any prerequisite is more recent than the
2408 `make' will run its commands unconditionally, regardless of
2418 The commands specified for `.DEFAULT' are used for any target for
2420 *Note Last Resort::. If `.DEFAULT' commands are specified, every
2422 will have these commands executed on its behalf. *Note Implicit
2428 execution of their commands, the target is not deleted. *Note
2467 changed and its commands exit with a nonzero exit status, just as
2473 ignore errors in execution of the commands run for those particular
2474 files. The commands for `.IGNORE' are not meaningful.
2477 ignore errors in execution of commands for all files. This usage
2481 specific commands. *Note Errors in Commands: Errors.
2485 assumes that these files are created by commands that generate low
2486 resolution time stamps. The commands for `.LOW_RESOLUTION_TIME'
2492 resolution file time stamp, so commands like `cp -p' that
2515 print the commands to remake those particular files before
2516 executing them. The commands for `.SILENT' are not meaningful.
2519 to print any commands before executing them. This usage of
2522 commands. *Note Command Echoing: Echoing. If you want to silence
2523 all commands for a particular run of `make', use the `-s' or
2554 with one target, and all identical aside from that. The same commands
2561 * You want just prerequisites, no commands. For example:
2568 * Similar commands work for all the targets. The commands do not
2571 the commands (*note Automatic Variables::). For example:
2589 target, much as the variable `$@' allows you to vary the commands. You
2603 the commands are executed.
2605 There can only be one set of commands to be executed for a file. If
2606 more than one rule gives commands for the same file, `make' uses the
2611 have the same target invoke multiple commands which are defined in
2641 If none of the explicit rules for a target has commands, then `make'
2642 searches for an applicable implicit rule to find some commands *note
2764 but it _does_ apply only when the target has no commands otherwise
2772 If two conflicting rules apply, and both have commands, that's an error.
2801 double-colon rule's commands are executed if the target is older than
2803 rule, its commands are always executed (even if the target already
2813 really make sense are those where the order of executing the commands
2821 Each double-colon rule should specify commands; if it does not, an
2937 The commands of a rule consist of one or more shell command lines to be
2939 result of executing these commands is that the target of the rule is
2942 Users use many different shell programs, but commands in makefiles
2949 * Echoing:: How to control when commands are echoed.
2950 * Execution:: How commands are executed.
2951 * Parallel:: How commands can be executed in parallel.
2955 * Sequences:: Defining canned sequences of commands.
2956 * Empty Commands:: Defining useful, do-nothing commands.
2966 Writing Makefiles: Makefiles.). However, commands are meant to be
3003 * Variables in Commands:: Using `make' variables in commands.
3038 consists of four separate shell commands where the output is:
3099 The other way in which `make' processes commands is by expanding any
3103 commands for targets which are not rebuilt are never expanded.
3105 Variable and function references in commands have identical syntax
3140 the commands yourself.
3151 commands, it won't execute them. *Note Summary of Options: Options
3152 Summary. In this case and only this case, even the commands starting
3154 commands `make' thinks are necessary without actually doing them.
3157 all commands started with `@'. A rule in the makefile for the special
3168 When it is time to execute commands to update a target, they are
3173 invoking shell commands such as `cd' that set a context local to each
3191 to run commands.
3216 _not_ exported in the environment to commands that `make' invokes.
3221 commands.
3291 GNU `make' knows how to execute several commands at once. Normally,
3294 tells `make' to execute many commands simultaneously.
3300 commands to execute at once; this is called the number of "job slots".
3305 One unpleasant consequence of running several commands
3306 simultaneously is that output generated by the commands appears
3307 whenever each command sends it, so messages from different commands may
3327 normally in all commands.
3392 are ignored in all commands of all rules. A rule in the makefile for
3405 further commands will be executed for these targets, since their
3489 You can write recursive `make' commands just by copying this example,
3492 it useful to declare targets that invoke recursive `make' commands as
3513 helps debug use of recursive `make' commands.
3521 Recursive `make' commands should always use the variable `MAKE', not
3533 As a special feature, using the variable `MAKE' in the commands of a
3545 commands; see *note Instead of Execution::.) Following the usual
3549 command, and `-t' says not to execute commands.
3555 commands not to be run. The usual `MAKEFLAGS' mechanism passes the
3558 commands, is propagated to the subsystem.
3671 `unexport' by themselves to have variables exported for some commands
3688 commands to use additional makefiles. The value of `MAKEFILES' is a
3832 When the same sequence of commands is useful in making various targets,
3838 Here is an example of defining a canned sequence of commands:
3846 marks the end of the definition; the lines in between are the commands.
3859 commands of a rule. You can substitute it like any other variable
3873 commands based on the file names involved (*note Using Implicit Rules:
3898 does not echo _any_ commands. (*Note Command Echoing: Echoing, for a
3907 It is sometimes useful to define commands which do nothing. This is
3919 target from getting implicit commands (from implicit rules or the
3938 explicit request into targets, prerequisites, commands, and other parts
3943 read, except for the shell commands in rules, the right-hand sides of
4005 prerequisites, commands, most directives, and new variable values.
4606 both canned sequences of commands (*note Defining Canned Command
4640 since two commands separated by semicolon behave much like two separate
4641 shell commands. However, note that using two separate lines means
4817 the makefile, so they _cannot_ be used to control shell commands at the
5052 conditionals because they are not defined until commands are run (*note
5098 the files to operate on or the commands to use. You use a function in a
5892 the commands for each rule (*note Automatic Variables::).
5977 The commands run by calls to the `shell' function are run when the
6082 kind of thing to do with the commands
6172 Another use of specifying a goal is to run the commands associated
6203 search for commands; copy any auxiliary files that the executable
6241 "No-op". The activity is to print what commands would be used to
6253 targets are up to date already; but execute no commands in either
6266 With the `-n' flag, `make' prints the commands that it would
6269 With the `-t' flag, `make' ignores the commands in the rules and
6275 With the `-q' flag, `make' prints nothing and executes no commands,
6299 commands, the `-W' flag can direct `make' to act as if some files
6321 can use the `-t' flag. This flag tells `make' not to run the commands
6408 gives up immediately, returning a nonzero status. No further commands
6423 addition to continuing after failed shell commands, `make -k' will
6531 Ignore all errors in commands executed to remake files. *Note
6543 Specifies the number of jobs (commands) to run simultaneously.
6547 information on how commands are run. Note that this option is
6560 Specifies that no new jobs (commands) should be started if there
6578 Print the commands that would be executed, but do not execute them.
6604 "Question mode". Do not run any commands, or print anything; just
6635 Silent operation; do not print the commands as they are executed.
6650 instead of running their commands. This is used to pretend that
6651 the commands were done, in order to fool future invocations of
6664 down errors from complicated nests of recursive `make' commands.
6713 The built-in implicit rules use several variables in their commands
6728 to get the commands for updating a file.
6733 * Last Resort:: How to define commands for rules which
6746 all you have to do is refrain from specifying commands yourself. Either
6760 If an implicit rule is found, it can supply both commands and one or
6790 for each double-colon rule, that has no commands. A file that is
6810 no commands, you can give that target empty commands by writing a
7006 However, the commands in built-in implicit rules actually use
7008 values contain the commands listed above.
7032 The commands in built-in implicit rules make liberal use of certain