Lines Matching refs:commands
8 and issues the commands to recompile them.
61 commands of implicit rules.
110 and commands. If a pattern rule has multiple targets, `make' knows that
111 the rule's commands are responsible for making all of the targets. The
112 commands are executed only once to make all the targets. When searching
115 incidental: `make' worries only about giving commands and prerequisites
116 to the file presently in question. However, when this file's commands
206 target caused the rule's commands to be run.
216 commands from an implicit rule, this will be the first
237 primarily useful for use in linking commands where it is
432 considered. These dummy rules have no prerequisites and no commands,
454 prerequisites, but different commands. When the new rule is defined,
459 with the same target and prerequisites, but no commands. For example,
474 commands are used for all targets and prerequisites that have no
475 commands of their own and for which no other implicit rule applies.
487 You can instead define commands to be used for targets for which
488 there are no rules at all, even ones which don't specify commands. You
490 commands are used for all prerequisites which do not appear as targets
494 If you use `.DEFAULT' with no commands or prerequisites:
498 the commands previously stored for `.DEFAULT' are cleared. Then `make'
501 If you do not want a target to get the commands from a match-anything
502 pattern rule or `.DEFAULT', but you also do not want any commands to be
503 run for the target, you can give it empty commands (*note Defining
565 Suffix rules with no commands are also meaningless. They do not
566 remove previous rules as do pattern rules with no commands (*note
603 with no commands, for each target of ordinary rules none of which have
604 commands, and for each prerequisite that is not the target of any rule.
628 4. Remove from the list all rules with no commands.
663 applies. In that case, give T the same commands that `.DEFAULT'
664 has. Otherwise, there are no commands for T.
669 commands to remake the target file T are executed. After these
670 commands are executed, each of these stored file names are entered into
674 When the commands of a pattern rule are executed for T, the automatic
709 commands! Most programs that you might use in commands do not support
712 Therefore, valid commands to update an archive member target probably
760 of a file `bar.c' is enough to cause the following commands to be run,
827 `ar' commands run at the same time on the same archive file, they will
831 circumvent this problem by serializing all commands that operate on the
918 * Execution of recursive commands to run `make' via the variable
929 commands is retained when the commands are printed, so they appear
1121 just those without commands. This means you can do:
1137 no commands, and it is treated as if it had empty commands (*note
1144 We feel that it is cleaner for a rule without commands to always
1175 * Install Command Categories:: Three categories of commands in the `install'
1264 Write the Makefile commands (and any shell scripts, such as
1319 Makefiles should provide variables for overriding certain commands,
1345 of `CFLAGS', by writing them explicitly in the compilation commands or
1372 644'.) Then it should use those variables as the commands for actual
1390 the installation commands. Use a separate command for each file to be
1568 The Makefile commands should check whether the value of
1741 The commands should create all the directories in which files are
1777 commands into three categories: normal ones, "pre-installation"
1778 commands and "post-installation" commands. *Note Install Command
1807 The uninstallation commands are divided into three categories,
1808 just like the installation commands. *Note Install Command
1884 To help make users aware of this, the commands for the special
2012 When writing the `install' target, you must classify all the commands
2013 into three categories: normal ones, "pre-installation" commands and
2014 "post-installation" commands.
2016 Normal commands move files into their proper places, and set their
2020 Pre-installation and post-installation commands may alter other
2024 Pre-installation commands are typically executed before the normal
2025 commands, and post-installation commands are typically run after the
2026 normal commands.
2035 Most programs don't need any pre-installation commands, but we have
2038 To classify the commands in the `install' rule into these three
2040 specifies the category for the commands that follow.
2052 $(PRE_INSTALL) # Pre-install commands follow.
2053 $(POST_INSTALL) # Post-install commands follow.
2054 $(NORMAL_INSTALL) # Normal commands follow.
2057 rule, all the commands are classified as normal until the first category
2058 line. If you don't use any category lines, all the commands are
2063 $(PRE_UNINSTALL) # Pre-uninstall commands follow.
2064 $(POST_UNINSTALL) # Post-uninstall commands follow.
2065 $(NORMAL_UNINSTALL) # Normal commands follow.
2072 dependency's commands with a category line, and start the main target's
2073 commands with a category line also. This way, you can ensure that each
2077 Pre-installation and post-installation commands should not run any
2086 The reason for distinguishing the commands in this way is for the
2090 installation commands. But installing the binary package does need to
2091 execute the pre-installation and post-installation commands.
2094 pre-installation and post-installation commands. Here is one way of
2095 extracting the pre-installation commands (the `-s' option to `make' is
2323 Evaluate TEXT then read the results as makefile commands. Expands
2401 shell used to run commands. *Note Command Execution: Execution.
2412 commands has special meaning. *Note How the `MAKE' Variable
2495 `commands commence before first target. Stop.'
2496 `missing rule before commands. Stop.'
2534 `warning: overriding commands for target `XXX''
2535 `warning: ignoring old commands for target `XXX''
2536 GNU `make' allows commands to be specified only once per target
2537 (except for double-colon rules). If you give commands for a target
2538 which already has been defined to have commands, this warning is
2539 issued and the second set of commands will overwrite the first set.
3279 * # (comments), in commands: Command Syntax. (line 27)
3297 * +, and commands: MAKE Variable. (line 18)
3302 * - (in commands): Errors. (line 19)
3497 * @ (in commands): Echoing. (line 6)
3501 * \ (backslash), in commands: Splitting Lines. (line 6)
3530 * backslash (\), in commands: Splitting Lines. (line 6)
3563 * commands: Rule Syntax. (line 26)
3564 * commands setting shell variables: Execution. (line 10)
3565 * commands, backslash (\) in: Splitting Lines. (line 6)
3566 * commands, comments in: Command Syntax. (line 27)
3567 * commands, echoing: Echoing. (line 6)
3568 * commands, empty: Empty Commands. (line 6)
3569 * commands, errors in: Errors. (line 6)
3570 * commands, execution: Execution. (line 6)
3571 * commands, execution in parallel: Parallel. (line 6)
3572 * commands, expansion: Shell Function. (line 6)
3573 * commands, how to write: Commands. (line 6)
3574 * commands, instead of executing: Instead of Execution.
3576 * commands, introduction to: Rule Introduction. (line 8)
3577 * commands, quoting newlines in: Splitting Lines. (line 6)
3578 * commands, sequences of: Sequences. (line 6)
3579 * commands, splitting: Splitting Lines. (line 6)
3580 * commands, using variables in: Variables in Commands.
3582 * comments, in commands: Command Syntax. (line 27)
3602 * deducing commands (implicit rules): make Deduces. (line 6)
3621 * directory search (VPATH), and shell commands: Commands/Search.
3635 * echoing of commands: Echoing. (line 6)
3638 * empty commands: Empty Commands. (line 6)
3645 * errors (in commands): Errors. (line 6)
3651 * execution, of commands: Execution. (line 6)
3813 * newline, quoting, in commands: Splitting Lines. (line 6)
3853 * post-installation commands: Install Command Categories.
3855 * pre-installation commands: Install Command Categories.
3887 * printing of commands: Echoing. (line 6)
3898 * quoting newline, in commands: Splitting Lines. (line 6)
3945 * rule commands: Commands. (line 6)
3962 * rule, no commands or prerequisites: Force Targets. (line 6)
3992 * sequences of commands: Sequences. (line 6)
4004 * shell variables, setting in commands: Execution. (line 10)
4024 * splitting commands: Splitting Lines. (line 6)
4053 * syntax of commands: Command Syntax. (line 6)
4055 * tab character (in commands): Rule Syntax. (line 26)
4105 * variable references in commands: Variables in Commands.
4172 * writing rule commands: Commands. (line 6)
4224 * .DEFAULT, and empty commands: Empty Commands. (line 16)