Lines Matching refs:environment
114 * MAKEFILES Variable:: The environment can specify extra makefiles.
214 * Environment:: Variable values can come from the environment.
821 * MAKEFILES Variable:: The environment can specify extra makefiles.
1014 If the environment variable `MAKEFILES' is defined, `make' considers
1024 usually is not desirable to set the environment variable before a
1031 Some users are tempted to set `MAKEFILES' in the environment
1743 simulated by setting the environment variable HOME.
3209 environment. This is because the `SHELL' environment variable is used
3216 _not_ exported in the environment to commands that `make' invokes.
3217 Instead, the value inherited from the user's environment, if any, is
3220 Variables/Recursion.), forcing it to be passed in the environment to
3224 environment *is* used, since on those systems most users do not set
3276 where `SHELL' is set from the Makefile; if it is set in the environment
3502 default, an environment variable `CURDIR' will not override this
3567 through the environment by explicit request. These variables are
3573 its value to the environment for running each command. The sub-`make',
3574 in turn, uses the environment to initialize its table of variable
3578 either defined in the environment initially or set on the command line,
3580 Some shells cannot cope with environment variable names consisting of
3584 the value of the `SHELL' variable from the invoking environment is
3680 up the environment for a command.
3690 the outer-level makefile, is passed down through the environment; then
3708 its environment. In response, it takes the flags from that value and
3753 fixed limit on the size of the environment, and putting so much
3779 `MAKEFLAGS' in your environment. You can also set `MAKEFLAGS' in a
3786 environment or from a makefile), it first prepends a hyphen if the value
3793 If you do put `MAKEFLAGS' in your environment, you should be sure not
3955 and with some shells they cannot be passed through the environment to a
3986 * Environment:: Variable values can come from the environment.
4392 * Variables in the environment become `make' variables. *Note
4662 Variables in `make' can come from the environment in which `make' is
4663 run. Every environment variable that `make' sees when it starts up is
4666 argument, overrides the environment. (If the `-e' flag is specified,
4667 then values from the environment override assignments in the makefile.
4671 Thus, by setting the variable `CFLAGS' in your environment, you can
4677 environment.)
4680 are placed into the environment of that command. This allows you to
4682 Recursion.). By default, only variables that came from the environment
4687 Other use of variables from the environment is not recommended. It
4689 environment variables set up outside their control, since this would
4694 which is normally present in the environment to specify the user's
4696 choice to affect `make'; so, `make' handles the `SHELL' environment
4742 environment if the `-e' option is in force) will take precedence.
5774 value of your `$PATH' environment variable, since the `value' function
5871 `environment'
5872 if VARIABLE was defined as an environment variable and the `-e'
5876 `environment override'
5877 if VARIABLE was defined as an environment variable and the `-e'
5898 you run the command `make -f bar', even if the environment contains a
5907 ifeq "$(origin bletch)" "environment"
5912 If `bletch' has been defined from the environment, this will redefine
5916 from the environment, even under `-e', you could instead write:
5918 ifneq "$(findstring environment,$(origin bletch))" ""
5923 either `environment' or `environment override'. *Note Functions for
6514 `--environment-overrides'
6515 Give variables taken from the environment precedence over
6645 environment.
7034 the makefile, with arguments to `make', or in the environment to alter
7059 environment. To see the complete list of predefined variables for your