Searched refs:rules (Results 1 – 25 of 72) sorted by relevance
123
/ndk/sources/host-tools/make-3.81/tests/scripts/features/ |
D | targetvars | 7 rules, semicolon interference, etc."; 48 # Test target-specific vars with pattern/suffix rules 53 # Target-specific vars with multiple LHS pattern rules 206 # Test double-colon rules with target-specific variable values 236 # Test double-colon rules with target-specific variable values and 244 # Test double-colon rules with pattern-specific variable values 276 touch('t1/rules.mk'); 280 include rules.mk 283 foo.x : rules.mk ; @echo MYVAR=$(MYVAR) FOOVAR=$(FOOVAR) ALLVAR=$(ALLVAR) 286 rules.mk : MYVAR = foo [all …]
|
D | mult_rules | 3 of multiple rules for one target. One file can be the 4 target of several rules if at most one rule has commands; 5 the other rules can only have dependencies."; 8 The makefile created in this test contains two hardcoded rules
|
D | reinvoke | 18 all: ; @echo running rules. 25 '', "rebuilding incl.mk\nrunning rules.\n"); 31 run_make_test(undef, '', "rebuilding #MAKEFILE#\nrunning rules.\n");
|
D | patternrules | 3 $description = "Test pattern rules."; 48 # TEST #2: make sure files that are built via implicit rules are marked 100 # that are built via implicit rules (Savannah bug #13218).
|
D | statipattrules | 2 $description = "Test handling of static pattern rules."; 43 # TEST #3 -- PR/1670: don't core dump on invalid static pattern rules
|
D | order_only | 83 # Test order-only in pattern rules 108 # prerequisites in pattern rules.
|
D | double_colon | 2 $description = "Test handling of double-colon rules."; 128 # TEST 9: make sure all rules in s double colon family get executed
|
D | se_explicit | 2 $description = "Test second expansion in ordinary rules.";
|
D | mult_targets | 3 ."many rules, each with one target, and all identical aside\n"
|
D | se_statpat | 2 $description = "Test second expansion in static pattern rules.";
|
/ndk/sources/host-tools/make-3.81/ |
D | rule.c | 545 register unsigned int rules, terminal; in print_rule_data_base() local 550 rules = terminal = 0; in print_rule_data_base() 553 ++rules; in print_rule_data_base() 562 if (rules == 0) in print_rule_data_base() 566 printf (_("\n# %u implicit rules, %u"), rules, terminal); in print_rule_data_base() 568 printf (" (%.1f%%)", (double) terminal / (double) rules * 100.0); in print_rule_data_base() 571 int f = (terminal * 1000 + 5) / rules; in print_rule_data_base() 578 if (num_pattern_rules != rules) in print_rule_data_base() 584 num_pattern_rules, rules); in print_rule_data_base()
|
D | NEWS | 30 prerequisites of both explicit and implicit (pattern) rules. In order 33 feature is enabled then after all rules have been parsed the 37 such as $$(notdir $$@) etc. This behavior applies to implicit rules, 164 This syntax is only valid within explicit and static pattern rules: it 165 cannot be used in implicit (suffix or pattern) rules. Edouard G. Parmelan 312 LD, AR, etc.). Specifying this option forces -r (--no-builtin-rules) 356 Make defines new default rules for DOS-style C++ file naming 357 conventions, with ``.cpp'' suffixes. All the same rules as for 374 COMPATIBILITY: This new syntax means that if you have any rules where 491 for linking rules, where library files sometimes need to be listed twice [all …]
|
/ndk/sources/host-tools/make-3.81/tests/scripts/options/ |
D | dash-f | 6 ."we then call make with the rules from the concatenated \n" 8 ."rules in one call to make and checks that the output\n" 65 # Run Make again with ALL three rules in the order 2 1 3 to make sure 66 # that all rules are executed in the proper order
|
D | dash-l | 8 This test creates a makefile where all depends on three rules 12 the temp file again. Thus if any of the rules are run in
|
D | dash-t | 12 # The 'obvious' fix didn't work for double-colon rules, so pay special
|
/ndk/sources/host-tools/make-3.81/tests/scripts/misc/ |
D | general4 | 21 # Test implicit rules 45 # Test implicit rules with '$' in the name (see se_implicit) 57 # Test implicit rules with '$' in the name (see se_implicit)
|
/ndk/sources/host-tools/sed-4.2.1/testsuite/ |
D | mac-mf.sed | 1 # Rewrite default rules from .c.o: to .c.o: .c 121 # Comment out .PHONY rules. 123 # Comment out .SUFFIXES rules. 125 # Comment out .PRECIOUS rules. 127 ## Comment out default rules.
|
/ndk/sources/host-tools/make-3.81/tests/scripts/functions/ |
D | shell | 8 # Test shells inside rules.
|
/ndk/sources/host-tools/make-3.81/tests/scripts/targets/ |
D | FORCE | 3 $description = "The following tests rules without Commands or Dependencies.";
|
D | INTERMEDIATE | 14 Try this with implicit rules and explicit rules: both should work.\n";
|
D | PHONY | 4 ."sure that the rules under a target get executed even if\n"
|
/ndk/sources/host-tools/make-3.81/doc/ |
D | make.info-2 | 51 Note that expansion using `%' in pattern rules occurs *after* any 58 * Pattern Intro:: An introduction to pattern rules. 59 * Pattern Examples:: Examples of pattern rules. 61 commands of implicit rules. 64 defining rules that can match any 66 * Canceling Rules:: How to override or cancel built-in rules. 108 Pattern rules may have more than one target. Unlike normal rules, 109 this does not act as many different rules with the same prerequisites 119 The order in which pattern rules appear in the makefile is important 121 applicable rules, only the first one found is used. The rules you [all …]
|
D | make.texi | 100 * Implicit Rules:: Use implicit rules to treat many files alike, 164 * Multiple Rules:: How to use several rules with the same target. 165 * Static Pattern:: Static pattern rules apply to multiple targets 169 several independent rules for one target. 170 * Automatic Prerequisites:: How to automatically generate rules giving 189 * Implicit/Search:: How search paths affect implicit rules. 194 * Static Usage:: The syntax of static pattern rules. 195 * Static versus Implicit:: When are they better than implicit rules? 293 * Catalogue of Rules:: A list of built-in implicit rules. 294 * Implicit Variables:: How to change what predefined rules do. [all …]
|
D | make.info-1 | 75 * Implicit Rules:: Use implicit rules to treat many files alike, 138 * Multiple Rules:: How to use several rules with the same target. 139 * Static Pattern:: Static pattern rules apply to multiple targets 143 several independent rules for one target. 144 * Automatic Prerequisites:: How to automatically generate rules giving 163 * Implicit/Search:: How search paths affect implicit rules. 168 * Static Usage:: The syntax of static pattern rules. 169 * Static versus Implicit:: When are they better than implicit rules? 267 * Catalogue of Rules:: A list of built-in implicit rules. 268 * Implicit Variables:: How to change what predefined rules do. [all …]
|
/ndk/sources/host-tools/sed-4.2.1/po/ |
D | Rules-quot | 1 # Special Makefile rules for English message catalogs with quotation marks.
|
123