HomeSort by: relevance | last modified time | path
    Searched refs:variables (Results 1 - 25 of 105) sorted by relevancy

1 2 3 4 5

  /src/usr.bin/make/unit-tests/
var-scope-global.mk 3 # Tests for global variables, which are the most common variables.
5 # Global variables can be assigned and appended to.
12 # Global variables can be removed from their scope.
depsrc.exp 1 : 'Undefined variables are expanded directly in the dependency'
3 : 'This is in contrast to local variables such as ${.TARGET}.'
directive-unexport.mk 11 # First, export 3 variables.
17 # Show the exported variables and their values.
23 # XXX: Now try to unexport all of them. The variables are still exported
depsrc.mk 10 # Demonstrate when exactly undefined variables are expanded in a dependency
18 : 'Undefined variables are expanded directly in the dependency'
20 : 'This is in contrast to local variables such as $${.TARGET}.'
23 : 'Undefined variables are tried to be expanded in a dependency'
opt-debug.mk 5 # Enable debug logging for the variables (var.c).
var-scope-local-legacy.mk 3 # Tests for legacy target-local variables, such as ${<F} or ${@D}.
7 # as the target-specific variables are not available either. The expressions
13 # It's possible to define variables of the legacy name in the global or
14 # command line scope, and they override the target-local variables, leading to
23 # Only variables of length 2 can be legacy, this one cannot.
28 # variables, 'A' is not such a character.
directive-export.mk 32 # argument exported all global variables. This case could be triggered
38 # An empty argument means no additional variables to export.
43 # or for the ':sh' modifier, all variables that were marked for being exported
45 # running a child command, the marked-as-exported variables would need to be
47 # don't export the variables while preparing a child process, see
56 # that only subprocesses access the environment variables. The ':localtime'
66 _!= echo 'force exporting the environment variables'
directive-for-errors.exp 8 make: directive-for-errors.mk:52: Missing iteration variables in .for loop
9 make: directive-for-errors.mk:64: Wrong number of words (5) in .for substitution list with 3 variables
varname-make_print_var_on_error.mk 4 # values of selected variables on error.
15 # does not expand the node-local variables like .TARGET. This results in the
cond-undef-lint.mk 3 # Tests for defined and undefined variables in .if conditions, in lint mode.
6 # accurate error messages in case of undefined variables, instead of the
52 # Variables that are referenced indirectly may be undefined in a condition.
55 # and a few others. Just because these nested variables are not defined,
60 # variables. In particular, there is no modifier that would turn undefined
61 # nested variables into empty strings, as an equivalent to the :U modifier.
var-scope-local.mk 3 # Tests for target-local variables, such as ${.TARGET} or $@. These variables
5 # target. In contrast, global variables are typically created when the
8 # The 7 built-in target-local variables are listed in the manual page. They
10 # target-local variables can be defined in dependency lines like
15 # Target-local variables in a target rule
56 # Target-local variables in an inference rule
61 # Target-local variables in a chain of inference rules
73 # The target-local variables can be used in expressions, just like other
74 # variables. When these expressions are evaluated outside of a target, thes
    [all...]
posix1.exp 11 Local variables
16 Directory and filename parts of local variables
51 Local variables
56 Directory and filename parts of local variables
97 Local variables
102 Directory and filename parts of local variables
144 Local variables
149 Directory and filename parts of local variables
varname-dot-makeflags.mk 28 # when parsing the makefiles. This is different from exported variables,
35 # special variables '.MAKEFLAGS' and '.MAKEOVERRIDES'.
varname-make_print_var_on_error-jobs.mk 4 # values of selected variables on error.
17 # does not expand the node-local variables like .TARGET. This results in the
directive-export-impl.mk 3 # Test for the implementation of exporting variables to child processes.
4 # This involves marking variables for export, actually exporting them,
36 # variables exported. Since this variable has both of the above-mentioned
39 # evaluated, the referenced variables could have changed, therefore the
opt-x-reduce-exported.mk 3 # Tests for the -X command line option, which prevents variables passed on the
cond-late.mk 11 # Because of this, variables that are used in these lazy conditions
34 # and then expand the variables, the output would change from the
35 # current "yes no" to "yes yes", since both variables are non-empty.
directive-for-empty.mk 17 # replacement creates the impression that .for variables were real variables,
30 # variables were real variables, calling 'empty' would work on them as well.
37 # The typical way of mistakenly using 'empty' with variables from .for loops
42 # Instead of the 'empty' function, the variables from .for loops can be
82 # An idea to work around the above problems is to collect the variables from
99 # that variables from .for loops can only affect expressions in the current
100 # file. If variables from .for loops were implemented as global variables,
    [all...]
opt-env.mk 3 # Tests for the -e command line option, which looks up environment variables
4 # before those from the global scope. It has no influence on variables from
43 # which is independent from the environment variables.
recursive.mk 8 # whether there are unclosed variables. The variable value is therefore
29 # The purpose of the -dL flag is to detect unclosed variables. This
33 # variables are not discovered. But these are hard to produce anyway,
var-scope-cmdline.mk 3 # Tests for variables specified on the command line.
5 # Variables that are specified on the command line override those from the
13 # most of the variables are stored. This conflicts with the statement that
14 # variables from the cmdline scope override global variables, since after the
57 # that both global and cmdline variables could now be undefined at will as a
61 # Most cmdline variables are set at the very beginning, when parsing the
63 # possible to set cmdline variables at any later time.
directive-undef.mk 39 # words, just like everywhere else. This prevents variables whose names
41 # undefined, but these characters do not appear in variables names anyway.
47 .undef ${VARNAMES} # undefines the variables "1", "2" and "3"
57 # for such variables anyway.
122 # Deletes the variables from the global scope and also from the environment.
123 # This applies to both variables, even though 'INDIRECT' is not actually
directive-for.mk 5 # TODO: Describe naming conventions for the loop variables.
16 # values depending on other variables. In simple cases, the same effect can
27 # The .for loop also works for multiple iteration variables.
51 # In the body of the .for loop, the iteration variables can be accessed
52 # like normal variables, even though they are not really variables.
59 # iteration variables and the normal global variables live in separate
61 # variables is restricted to the current makefile, it does not reach over to
88 # Before for.c 1.39 from 2008-12-21, the values of the iteration variables
    [all...]
  /src/usr.bin/mail/
vars.c 107 for (vp = variables[hash(name)]; vp != NULL; vp = vp->v_link)
127 vp->v_link = variables[h];
128 variables[h] = vp;
  /src/usr.sbin/sysinst/arch/luna68k/
msg.md.en 57 firmware NVRAM variables to load NetBSD's bootloader by default.
59 To boot NetBSD, you need to set boot NVRAM variables 'drv'

Completed in 255 milliseconds

1 2 3 4 5