Lines Matching full:suffix
255 suffix (*note Old-Fashioned Suffix Rules: Suffix Rules.), `$*' is
256 set to the target name minus the suffix. For example, if the
258 suffix. GNU `make' does this bizarre thing only for compatibility
263 recognized suffix, `$*' is set to the empty string for that rule.
344 A target pattern is composed of a `%' between a prefix and a suffix,
346 only if the file name starts with the prefix and ends with the suffix,
347 without overlap. The text between the prefix and the suffix is called
356 before it is compared with the target prefix and suffix. After the
427 as executable files) and a file name with a recognized suffix indicates
443 suffix listed as valid for use in suffix rules (*note Old-Fashioned
444 Suffix Rules: Suffix Rules.).
465 File: make.info, Node: Last Resort, Next: Suffix Rules, Prev: Pattern Rules, Up: Implicit Rules
510 File: make.info, Node: Suffix Rules, Next: Implicit Rule Search, Prev: Last Resort, Up: Implicit Rules
512 10.7 Old-Fashioned Suffix Rules
515 "Suffix rules" are the old-fashioned way of defining implicit rules for
516 `make'. Suffix rules are obsolete because pattern rules are more
519 "double-suffix" and "single-suffix".
521 A double-suffix rule is defined by a pair of suffixes: the target
522 suffix and the source suffix. It matches any file whose name ends with
523 the target suffix. The corresponding implicit prerequisite is made by
524 replacing the target suffix with the source suffix in the file name. A
525 two-suffix rule whose target and source suffixes are `.o' and `.c' is
528 A single-suffix rule is defined by a single suffix, which is the
529 source suffix. It matches any file name, and the corresponding implicit
530 prerequisite name is made by appending the source suffix. A
531 single-suffix rule whose source suffix is `.c' is equivalent to the
534 Suffix rule definitions are recognized by comparing each rule's
536 rule whose target is a known suffix, this rule is considered a
537 single-suffix rule. When `make' sees a rule whose target is two known
538 suffixes concatenated, this rule is taken as a double-suffix rule.
542 `make' takes it to be a double-suffix rule with source suffix `.c' and
543 target suffix `.o'. Here is the old-fashioned way to define the rule
549 Suffix rules cannot have any prerequisites of their own. If they
551 suffix rules. Thus, the rule:
565 Suffix rules with no commands are also meaningless. They do not
568 suffix or pair of suffixes concatenated as a target in the data base.
585 .SUFFIXES: .c .o .h # Define our suffix list
596 File: make.info, Node: Implicit Rule Search, Prev: Suffix Rules, Up: Implicit Rules
608 Suffix rules are not mentioned in this algorithm because suffix
693 * Archive Suffix Rules:: You can write a special kind of suffix rule
820 File: make.info, Node: Archive Pitfalls, Next: Archive Suffix Rules, Prev: Archive Update, Up: Archives
836 File: make.info, Node: Archive Suffix Rules, Prev: Archive Pitfalls, Up: Archives
838 11.4 Suffix Rules for Archive Files
841 You can write a special kind of suffix rule for dealing with archive
842 files. *Note Suffix Rules::, for a full explanation of suffix rules.
843 Archive suffix rules are obsolete in GNU `make', because pattern rules
847 To write a suffix rule for archives, you simply write a suffix rule
848 using the target suffix `.a' (the usual suffix for archive files). For
849 example, here is the old-fashioned suffix rule to update a library
864 In fact, this is just what `make' does when it sees a suffix rule
865 with `.a' as the target suffix. Any double-suffix rule `.X.a' is
869 Since you might want to use `.a' as the suffix for some other kind
870 of file, `make' also converts archive suffix rules to pattern rules in
871 the normal way (*note Suffix Rules::). Thus a double-suffix rule
922 * Support for suffix `.a' in suffix rules. *Note Archive Suffix
1043 * Allow suffixes for suffix rules (*note Old-Fashioned Suffix Rules:
1044 Suffix Rules.) to contain any characters. In other versions of
1093 * Suffixes (used in suffix rules) that end with the character `~'
1096 For example, the suffix rule `.c~.o' would make the file `N.o' from
1098 such suffix rules is required. *Note Old-Fashioned Suffix Rules:
1099 Suffix Rules.
1136 * It appears that in SVR4 `make', a suffix rule can be specified with
1142 will override the built-in `.c.a' suffix rule.
1192 Different `make' programs have incompatible suffix lists and
1194 it is a good idea to set the suffix list explicitly using only the
1200 The first line clears out the suffix list, the second introduces all
2252 `$(suffix NAMES...)'
2253 Extract the suffix (the last `.' and following characters) of each
2258 Extract the base name (name without suffix) of each file name.
2261 `$(addsuffix SUFFIX,NAMES...)'
2262 Append SUFFIX to each word in NAMES.
3454 * .a (archives): Archive Suffix Rules.
3516 * archive, suffix rule for: Archive Suffix Rules.
3670 * file name suffix: File Name Functions. (line 43)
3671 * file name suffix, adding: File Name Functions. (line 68)
3756 * library archive, suffix rule for: Archive Suffix Rules.
3823 * old-fashioned suffix rules: Suffix Rules. (line 6)
4045 * suffix rule: Suffix Rules. (line 6)
4046 * suffix rule, for archive: Archive Suffix Rules.
4048 * suffix, adding: File Name Functions. (line 68)
4049 * suffix, function to find: File Name Functions. (line 43)
4050 * suffix, substituting in variables: Substitution Refs. (line 6)
4135 * variables, substituting suffix in: Substitution Refs. (line 6)
4249 * .SUFFIXES <1>: Suffix Rules. (line 61)
4373 * suffix: File Name Functions. (line 43)
4374 * SUFFIXES: Suffix Rules. (line 81)
