Home
last modified time | relevance | path

Searched refs:variables (Results 1 – 25 of 77) sorted by relevance

1234

/ndk/sources/host-tools/make-3.81/tests/scripts/options/
Dwarn-undefined-variables3 $description = "Test the --warn-undefined-variables option.";
5 $details = "Verify that warnings are printed for referencing undefined variables.";
7 # Without --warn-undefined-variables, nothing should happen
19 # With --warn-undefined-variables, it should warn me
20 run_make_test(undef, '--warn-undefined-variables',
/ndk/sources/host-tools/make-3.81/tests/scripts/functions/
Dshell14 # Test shells inside exported environment variables.
15 # This is the test that fails if we try to put make exported variables into
Dforeach36 # TEST 1: Test that foreach variables take precedence over global
37 # variables in a global scope (like inside an eval). Tests bug #11913
Dfilter-out5 $details = "The makefile created in this test has two variables. The
/ndk/sources/host-tools/make-3.81/tests/
DChangeLog49 * scripts/variables/negative: Test some variable reference failure
51 * scripts/options/warn-undefined-variables: Test the
52 --warn-undefined-variables flag.
74 * scripts/variables/automatic: Add a test for bug #8154.
107 * scripts/variables/INCLUDE_DIRS: Add a test for the .INCLUDE_DIRS
142 * scripts/variables/SHELL: Use a /./ prefix instead of //: the
167 variables are leaking out beyond the tests they are intended for.
173 * tests/scripts/variables/SHELL: Ditto.
207 * scripts/variables/MAKE_RESTARTS: New file: test the
235 * scripts/variables/DEFAULT_GOAL: Rename DEFAULT_TARGET to
[all …]
/ndk/sources/host-tools/make-3.81/tests/scripts/features/
Dse_explicit25 # TEST #1: automatic variables.
61 # Test #2: target/pattern -specific variables.
Dpatspecific_vars64 # TEST #5 -- test pattern-specific exported variables
74 # TEST #6 -- test expansion of pattern-specific simple variables
116 # TEST #7 -- test expansion of pattern-specific recursive variables
Dse_statpat6 # Test #1: automatic variables.
42 # Test #2: target/pattern -specific variables.
Dexport105 # TEST 6: Test the expansion of variables inside export
138 # TEST 7: Test the expansion of variables inside unexport
173 # TEST 7: Test exporting multiple variables on the same line
208 # TEST 8: Test unexporting multiple variables on the same line
Dse_implicit12 # Test #1: automatic variables.
61 # Test #2: target/pattern -specific variables.
Dtargetvars24 # Test per-target recursive variables
37 # Test the export keyword with per-target variables
136 # For PR/1380: Using += assignment in target-specific variables sometimes fails
252 # Test target-specific variables with very long command line
/ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/test/utils/runtime/env/
Dfwd.hpp19 #error Windows CE does not support environment variables.
Denvironment.hpp19 #error Windows CE does not support environment variables.
Dvariable.hpp19 #error Windows CE does not support environment variables.
/ndk/sources/host-tools/make-3.81/
DNEWS35 variables in scope. This means that in addition to using standard
73 * All pattern-specific variables that match a given target are now used
76 * Target-specific variables can be marked as exportable using the
88 * New special variables available in this release:
201 etc. as recursive variables, even though they are fully expanded
204 variables. This may mean that if you added extra escaping to your
208 variables it can reference itself and this will not produce an error
250 * Previously, GNU make quoted variables such as MAKEFLAGS and
258 With this version we change that behavior: now these variables are
260 correct way to do it. If you previously used these variables
[all …]
Dvariable.c447 struct variable_set_list *l = file->variables; in initialize_file_variables()
456 file->variables = l; in initialize_file_variables()
466 l->next = file->double_colon->variables; in initialize_file_variables()
475 l->next = file->parent->variables; in initialize_file_variables()
867 set_list = file->variables; in target_environment()
1479 if (file->variables != 0) in print_file_variables()
1480 print_variable_set (file->variables->set, "# "); in print_file_variables()
DINSTALL16 various system-dependent variables used during compilation. It uses
75 details on some of the pertinent environment variables.
78 by setting variables in the command line or in the environment. Here
175 values for variables like `CC', `cache_file', and `prefix'.
187 variables may be lost. In order to avoid this problem, you should set
Dfiledef.h50 struct variable_set_list *variables; member
/ndk/sources/host-tools/make-3.81/tests/scripts/variables/
Dspecial3 $description = "Test special GNU make variables.";
/ndk/sources/host-tools/make-3.81/doc/
Dmake.info-260 * Automatic Variables:: How to use automatic variables in the
140 uses the automatic variables `$@' and `$<' to substitute the names of
183 variables". These variables have values computed afresh for each rule
199 Here is a table of automatic variables:
273 Of the variables listed above, four have values that are single file
276 name within the directory. The variant variables' names are formed by
330 these automatic variables; we write "the value of `$<'", rather than
331 "the variable `<'" as we would write for ordinary variables such as
675 variables are set corresponding to the target and prerequisites. *Note
781 named `file.o'. In connection with such usage, the automatic variables
[all …]
Dmake-stds.texi171 and related programs, but should do so via @code{make} variables so that the
180 Use the following @code{make} variables to run those programs:
197 Additional utilities that can be used via Make variables are:
210 Makefiles should provide variables for overriding certain commands, options,
213 In particular, you should run most utility programs via variables.
219 so on, need not be referred to through variables in this way, since users
252 Put @code{CFLAGS} last in the compilation command, after other variables
262 Every Makefile should also define the variables @code{INSTALL_PROGRAM}
265 @code{$@{INSTALL@} -m 644}.) Then it should use those variables as the
267 respectively. Use these variables as follows:
[all …]
Dmake.texi95 * Using Variables:: You can use variables to avoid repetition.
97 on the values of variables.
142 * Special Variables:: Other special variables.
212 * Variables in Commands:: Using @code{make} variables in commands.
222 * Variables/Recursion:: How to communicate variables to a sub-@code{make}.
232 * Values:: All the ways variables get their values.
307 * Automatic Variables:: How to use automatic variables in the
718 @cindex variables
719 @cindex simplifying with variables
940 * Special Variables:: Other special variables.
[all …]
/ndk/sources/host-tools/make-3.81/po/
DMakevars18 # Makefile variables for PO directory in any package using GNU gettext.
23 # These two variables depend on the location of this directory.
/ndk/build/tools/
Dgen-system-symbols.sh208 (echo "$VARS" | tr ' ' '\n') > $DSTDIR/$LIB.variables.txt
/ndk/sources/host-tools/gdb-pretty-printers/stlport/gppfs-0.2/
DREADME37 the pretty printers work the variables from test.cpp should be displayed in a

1234