Lines Matching full:prerequisite
106 * Combine By Prerequisite:: Another Style of Makefile
127 * Prerequisite Types:: There are two types of prerequisites.
157 to every prerequisite.
448 * Combine By Prerequisite:: Another Style of Makefile
469 A "prerequisite" is a file that is used as input to create the
549 both a target and a prerequisite. Commands include `cc -c main.c' and
570 `clean' is not a prerequisite of any other rule. Consequently, `make'
572 this rule not only is not a prerequisite, it also does not have any
693 File: make.info, Node: make Deduces, Next: Combine By Prerequisite, Prev: Variables Simplify, Up: Introduction
740 File: make.info, Node: Combine By Prerequisite, Next: Cleanup, Prev: make Deduces, Up: Introduction
760 Here `defs.h' is given as a prerequisite of all the object files;
769 File: make.info, Node: Cleanup, Prev: Combine By Prerequisite, Up: Introduction
802 Since `clean' is not a prerequisite of `edit', this rule will not
1162 Supports secondary expansion of prerequisite lists.
1166 Prerequisites: Prerequisite Types.
1296 prerequisite `force', to guarantee that the commands will be run even
1300 itself and create a prerequisite loop!
1369 That is, the target and prerequisite sections are expanded
1372 suffix rules, static pattern rules, and simple prerequisite definitions.
1386 defined before the first prerequisite list that makes use of this
1429 Here the prerequisite of `onefile' will be expanded immediately, and
1430 resolve to the value `top', while the prerequisite of `twofile' will
1483 variable evaluates to the first prerequisite in the first rule for this
1497 In the first prerequisite list, all three variables (`$$<', `$$^',
1548 The prerequisite list after the secondary expansion and directory
1583 * Prerequisite Types:: There are two types of prerequisites.
1630 File: make.info, Node: Rule Syntax, Next: Prerequisite Types, Prev: Rule Example, Up: Rules
1662 if you really want a dollar sign in a target or prerequisite you must
1690 File: make.info, Node: Prerequisite Types, Next: Wildcards, Prev: Rule Syntax, Up: Rules
1697 section, and "order-only" prerequisites. A normal prerequisite makes
1702 prerequisite is newer than the target, then the target is considered
1705 Normally, this is exactly what you want: if a target's prerequisite
1721 file to be both a normal and an order-only prerequisite, the normal
1722 prerequisite takes precedence (since they are a strict superset of the
1723 behavior of an order-only prerequisite).
1726 File: make.info, Node: Wildcards, Next: Directory Search, Prev: Prerequisite Types, Up: Rules
1793 However, if you use the value of `objects' in a target, prerequisite or
1819 becomes a prerequisite of `foo' and will be recompiled if necessary.
1901 a prerequisite. When you redistribute the files among directories, you
1907 to every prerequisite.
1924 expected to contain prerequisite files that are not in the current
1928 Thus, if a file that is listed as a target or prerequisite does not
1931 them, that file may become the prerequisite (see below). Rules may then
1932 specify the names of files in the prerequisite list as if they all
1991 string must match the file name of a prerequisite that is being searched
1995 (If there is no `%', the pattern must match the prerequisite exactly,
2005 When a prerequisite fails to exist in the current directory, if the
2006 PATTERN in a `vpath' directive matches the name of the prerequisite
2014 tells `make' to look for any prerequisite whose name ends in `.h' in
2018 If several `vpath' patterns match the prerequisite file's name, then
2045 When a prerequisite is found through directory search, regardless of
2047 that `make' actually provides you in the prerequisite list. Sometimes
2067 prerequisite lists which contain this target. In short, if
2103 When a prerequisite is found in another directory through directory
2106 they will look for the prerequisite in the directory where `make' finds
2125 just the first prerequisite:
2160 prerequisite whose name is of the form `-lNAME'. (You can tell
2161 something strange is going on here because the prerequisite is normally
2165 When a prerequisite's name has the form `-lNAME', `make' handles it
2189 prerequisite like `-lNAME' is seen, `make' will replace the percent in
2291 A phony target should not be a prerequisite of a real target file;
2293 file. As long as a phony target is never a prerequisite of a real
2322 When one phony target is a prerequisite of another, it serves as a
2384 commands are executed if any prerequisite is more recent than the
2385 target; in other words, if a prerequisite has changed since the last
2421 file mentioned as a prerequisite, but not as a target in a rule,
2436 `%.o') as a prerequisite file of the special target `.PRECIOUS' to
2456 makefile, then all prerequisite lists defined _after_ it appears
2495 as a prerequisite of `.LOW_RESOLUTION_TIME' so that `make' does
2565 gives an additional prerequisite to each of the three object files
2602 the target. If the target is older than any prerequisite from any rule,
2628 form to use if you wish to add the additional prerequisite
2639 a prerequisite of each object file, but plain `make' will not.
2652 construct the prerequisite names for each target based on the target
2683 prerequisite names (one from each PREREQ-PATTERN).
2692 The prerequisite names for each target are made by substituting the
2693 stem for the `%' in each prerequisite pattern. For example, if one
2694 prerequisite pattern is `%.c', then substitution of the stem `foo'
2695 gives the prerequisite name `foo.c'. It is legitimate to write a
2696 prerequisite pattern that does not contain `%'; then this prerequisite
2721 prerequisite and `$@' is the automatic variable that holds the name of
2818 target differs depending on which prerequisite files caused the update,
2857 Note that such a prerequisite constitutes mentioning `main.o' in a
2873 The practice we recommend for automatic prerequisite generation is
2920 list of source files `foo.c bar.c' into a list of prerequisite
3854 prerequisite of whichever rule uses the canned sequence. The output
4761 Be aware that a given prerequisite will only be built once per
4762 invocation of make, at most. If the same file is a prerequisite of
4765 will cause that prerequisite to be built and the prerequisite will
5383 directories that `make' should search for prerequisite files (*note
6169 which has a rule in the makefile but is not a prerequisite of the
6425 how to make a target or prerequisite file. This will always cause an
6766 Each implicit rule has a target pattern and prerequisite patterns.
6777 know which possible prerequisite files are supposed to exist. *Note
6783 mentioned explicitly in the makefile as a target or a prerequisite, or
6785 an implicit prerequisite is the result of another implicit rule, we say
6791 mentioned only as a prerequisite is considered a target whose rule
6801 The prerequisite on `foo.p' does not necessarily mean that `make' will
7218 target, unless some prerequisite of B is newer than that target or
7228 makefile as a target or prerequisite. However, you can explicitly mark
7229 a file as intermediate by listing it as a prerequisite of the special
7235 prerequisite of the special target `.SECONDARY'. When a file is
7241 as a prerequisite of the special target `.PRECIOUS' to preserve
