Lines Matching refs:shell
161 * Commands/Search:: How to write shell commands that work together
190 * Choosing the Shell:: How `make' chooses the shell used
244 * Shell Function:: Substitute the output of a shell command.
318 with a shell command. Indeed, `make' is not limited to programs. You
341 files, this simple shell command:
397 with simple shell commands. Finally, be sure to explain what you
559 A shell command follows each line that contains a target and
560 prerequisites. These shell commands say how to update the target file.
881 the entire line is passed to the shell, just as with any other
882 line that begins with a TAB. The shell decides how to interpret
883 the text: whether or not this is a comment is up to the shell.
935 FILENAMES can contain shell file name patterns. If FILENAMES is empty,
1358 variables in a conditional you _must_ use shell conditional syntax, in
1686 executed by the shell (normally `sh'), but with some extra features
1733 in the Bourne shell. For example, `*.c' specifies a list of all the
1746 and in prerequisites. In commands the shell is responsible for
1768 by the shell. For example, here is a rule to delete all the object
1911 * Commands/Search:: How to write shell commands that work together
2253 shell loop over the subdirectories, like this:
2265 overcome by adding shell commands to note the error and exit, but then
2890 `-e' flag to the shell causes it to exit immediately if the `$(CC)'
2937 The commands of a rule consist of one or more shell command lines to be
2942 Users use many different shell programs, but commands in makefiles
2967 interpreted by the shell and so they are written using shell syntax.
2968 The `make' program does not try to understand shell syntax: it performs
2970 before handing it to the shell.
2986 passed to the shell as-is. Whether the shell treats it as a
2987 comment or not depends on your shell.
2992 shell.
2997 considered a command line and be passed to the shell.
3016 shell will be invoked to run it.
3021 to the shell. How the backslash-newline is interpreted depends on your
3022 shell. If the first character of the next line after the
3038 consists of four separate shell commands where the output is:
3051 will run one shell with a command script of:
3057 which, according to shell quoting rules, will yield the following
3066 with single quotes (`'...''). This is the way the default shell
3068 different shell in your makefiles it may treat them differently.
3108 command, you must double it (`$$'). For shells like the default shell,
3111 `make' variable (use a single dollar sign) or a shell variable (use two
3120 results in the following command being passed to the shell:
3143 The `@' is discarded before the command is passed to the shell.
3172 *Please note:* this implies that setting shell variables and
3173 invoking shell commands such as `cd' that set a context local to each
3176 command line. Then `make' will invoke one shell to run the entire
3177 line, and the shell will execute the statements in sequence. For
3183 Here we use the shell AND operator (`&&') so that if the `cd' command
3190 * Choosing the Shell:: How `make' chooses the shell used
3204 The program used as the shell is taken from the variable `SHELL'. If
3206 used as the shell.
3210 to specify your personal choice of shell program for interactive use.
3227 for `make', you can set the variable `MAKESHELL' to the shell that
3228 `make' should use; if set it will be used as the shell instead of the
3234 Choosing a shell in MS-DOS and MS-Windows is much more complex than on
3241 is different on MS-DOS. The stock shell, `command.com', is
3243 to install a replacement shell. Therefore, on MS-DOS, `make' examines
3245 points to a Unix-style or DOS-style shell. This allows reasonable
3248 If `SHELL' points to a Unix-style shell, `make' on MS-DOS
3249 additionally checks whether that shell can indeed be found; if not, it
3251 the shell in the following places:
3269 set to the full pathname of the shell as found. However, if none of
3272 only support features specific to a Unix-style shell if such a shell is
3275 Note that this extended search for the shell is limited to the cases
3278 shell, exactly as things are on Unix.
3367 After each shell command returns, `make' looks at its exit status. If
3369 in a new shell; after the last command line is finished, the rule is
3382 the command is passed to the shell for execution.
3645 `make' in the same way they work in the shell, `sh'.
3943 read, except for the shell commands in rules, the right-hand sides of
4081 slower; worse, it causes the `wildcard' and `shell' functions to give
4110 `:=' in conjunction with the `shell' function. (*Note The `shell'
4117 whoami := $(shell whoami)
4118 host-type := $(shell arch)
4641 shell commands. However, note that using two separate lines means
4642 `make' will invoke the shell twice, running an independent subshell for
4695 choice of interactive shell. It would be very undesirable for this
4817 the makefile, so they _cannot_ be used to control shell commands at the
5116 * Shell Function:: Substitute the output of a shell command.
5515 wildcard characters (as in shell file name patterns). The result
5569 (such as `shell' function calls, etc.)
5597 in the shell `sh' and the `foreach' command in the C-shell `csh'.
5962 8.11 The `shell' Function
5965 The `shell' function is unlike any other function other than the
5969 The `shell' function performs the same function that backquotes
5971 that it takes as an argument a shell command and evaluates to the
5977 The commands run by calls to the `shell' function are run when the
5979 Makefiles.). Because this function involves spawning a new shell, you
5981 `shell' function within recursively expanded variables vs. simply
5984 Here are some examples of the use of the `shell' function:
5986 contents := $(shell cat foo)
5991 files := $(shell echo *.c)
5994 strange shell, this has the same result as `$(wildcard *.c)' (as long
6213 Create a shell archive (shar file) of the source files.
6377 quoting in the shell to enclose spaces and other special characters in
6407 Normally, when an error happens in executing a shell command, `make'
6423 addition to continuing after failed shell commands, `make -k' will
6994 executable (by everyone). This is for shell scripts that are