Lines Matching refs:targets
158 or prerequisites to mark other targets
163 * Multiple Targets:: When to make use of several targets in a rule.
165 * Static Pattern:: Static pattern rules apply to multiple targets
244 to a group of targets that match a pattern.
317 * Archive Members:: Archive members as targets.
318 * Archive Update:: The implicit rule for archive member targets.
506 @cindex targets, introduction to
519 program; examples of targets are executable or object files. A target
539 which are the targets of the particular rule. @code{make} carries out
613 In the example makefile, the targets include the executable file
644 but are just actions are called @dfn{phony targets}. @xref{Phony
657 By default, @code{make} starts with the first target (not targets whose
659 (@dfn{Goals} are the targets that @code{make} strives ultimately to
690 The other rules are processed because their targets appear as
699 are not the targets of any rules---so @code{make} does nothing for these
852 you group entries by their prerequisites instead of by their targets.
961 called the rule's @dfn{targets}. It lists the other files that the
962 targets depend on, called the @dfn{prerequisites} of the target, and
963 may also give commands to use to create or update the targets.
1273 Sets the default goal to be used if no targets were specified on the
1337 @c @vindex .TARGETS @r{(list of targets)}
1340 @c value consists of a list of all targets defined in all makefiles read
1426 remake makefiles which are specified as targets of a double-colon rule
1448 targets to touch. So the @samp{-t} option has no effect on updating
1452 out-of-date makefile would result in the wrong output for other targets.
1477 include one in the other, and add more targets or variable definitions.
1489 to make the target @samp{foo} (and other targets), you can write a
1526 rules, and constructs a dependency graph of all the targets and their
1528 structures to determine what targets will need to be rebuilt and to
1615 prerequisites (only) for some or all targets defined in the makefile.
1622 prerequisites of the targets defined after the special target are
1690 @file{main} and @file{lib} targets will be @code{$($@@_OBJS)}. During
1815 certain files, called the rule's @dfn{targets} (most often only one per rule).
1824 rule in the first makefile. If the first rule has multiple targets,
1844 or prerequisites to mark other targets
1849 * Multiple Targets:: When to make use of several targets in a rule.
1851 * Static Pattern:: Static pattern rules apply to multiple targets
1899 @var{targets} : @var{prerequisites}
1908 @var{targets} : @var{prerequisites} ; @var{command}
1913 @cindex targets
1914 @cindex rule targets
1915 The @var{targets} are file names, separated by spaces. Wildcard
1947 A rule tells @code{make} two things: when the targets are out of date,
1998 @var{targets} : @var{normal-prerequisites} | @var{order-only-prerequisites}
2037 targets and in prerequisites. In commands the shell is responsible
2257 list for both prerequisites and targets of rules.
2593 @cindex phony targets
2594 @cindex targets, phony
2595 @cindex targets without a file
2635 Since it knows that phony targets do not name actual files that could be
2637 phony targets (@pxref{Implicit Rules}). This is why declaring a target
2652 Another example of the usefulness of phony targets is in conjunction
2676 take advantage of @code{make}'s ability to build targets in parallel
2679 By declaring the subdirectories as phony targets (you must do this as
2710 Phony targets can have prerequisites. When one directory contains multiple
2756 @cindex force targets
2757 @cindex targets, force
2763 been updated whenever its rule is run. This implies that all targets
2790 @cindex empty targets
2791 @cindex targets, empty
2792 @cindex recording events with empty targets
2827 @cindex special targets
2828 @cindex built-in special targets
2829 @cindex targets, built-in special
2831 Certain names have special meanings if they appear as targets.
2838 be phony targets. When it is time to consider such a target,
2862 @cindex precious targets
2865 The targets which @code{.PRECIOUS} depends on are given the following
2881 @cindex intermediate targets, explicit
2883 The targets which @code{.INTERMEDIATE} depends on are treated as
2889 @cindex secondary targets
2892 The targets which @code{.SECONDARY} depends on are treated as
2896 @code{.SECONDARY} with no prerequisites causes all targets to be treated
2914 @cindex removing targets on failure
3007 as @samp{.c.o}. These targets are suffix rules, an obsolete way of
3016 @cindex multiple targets
3017 @cindex several targets in a rule
3018 @cindex targets, multiple
3019 @cindex rule, with multiple targets
3021 A rule with multiple targets is equivalent to writing many rules, each with
3023 all the targets, but their effects may vary because you can substitute the
3025 the same prerequisites to all the targets also.
3042 Similar commands work for all the targets. The commands do not need
3075 You cannot do this with multiple targets in an ordinary rule, but you can
3147 @dfn{Static pattern rules} are rules which specify multiple targets and
3149 They are more general than ordinary rules with multiple targets because the
3150 targets do not have to have identical prerequisites. Their prerequisites must
3166 @var{targets} @dots{}: @var{target-pattern}: @var{prereq-patterns} @dots{}
3172 The @var{targets} list specifies the targets that the rule applies to.
3173 The targets can contain wildcard characters, just like the targets of
3189 the pattern @samp{%.o}, with @samp{foo} as the stem. The targets
3198 prerequisite is the same for all targets.
3287 By contrast, a static pattern rule applies to the precise list of targets
3289 invariably does apply to each of the targets specified. If two conflicting
3307 to precisely the targets specified.
3331 as rules with different targets are processed.
3704 commands for targets which are not rebuilt are never expanded.
4080 commands will be executed for these targets, since their preconditions
4089 continues to consider the other prerequisites of the pending targets,
4096 targets up to date; once @code{make} learns that this is impossible, it
4186 also find it useful to declare targets that invoke recursive
4245 @samp{-t} option marks targets as up to date without actually running
4643 When the same sequence of commands is useful in making various targets, you
4645 refer to the canned sequence from the rules for those targets. The canned
4765 You may be inclined to define empty command strings for targets that are
4780 substituted by explicit request into targets, prerequisites, commands,
4831 to a group of targets that match a pattern.
4847 Variable references can be used in any context: targets, prerequisites,
5818 multiple targets, and each of those targets has a different value for
5822 ignore the target-specific values from any other targets.
5867 will assign @code{CFLAGS} the value of @samp{-O} for all targets
7090 @code{make} variables, targets, implicit or explicit rules, etc.
7473 The @dfn{goals} are the targets that @code{make} should strive ultimately
7474 to update. Other targets are updated as well if they appear as
7478 targets that start with a period). Therefore, makefiles are usually
7481 targets, only the first target in the rule becomes the default goal, not
7494 targets not in the makefile may be specified, if @code{make} can find
7548 Make all the top-level targets the makefile knows about.
7567 Any of these targets might be defined to delete @emph{more} files than
7613 and how to update each target. But updating the targets is not always
7628 the targets up to date, but not actually execute them.
7637 ``Touch''. The activity is to mark the targets as up to date without
7639 the targets but does not really change their contents.
7647 ``Question''. The activity is to find out silently whether the targets
7680 targets to be considered are already up to date. If the exit status is
7847 consider the other prerequisites of the pending targets, remaking them
7885 Consider all targets out-of-date. GNU @code{make} proceeds to
7886 consider targets and their prerequisites using the normal algorithms;
7887 however, all targets so considered are always remade regardless of the
8012 prerequisites of these targets can be processed all the same.
8081 return an exit status that is zero if the specified targets are already
9028 commands. If a pattern rule has multiple targets, @code{make} knows that
9029 the rule's commands are responsible for making all of the targets. The
9030 commands are executed only once to make all the targets. When searching
9035 other targets are marked as having been updated themselves.
9036 @cindex multiple targets, in pattern rule
9083 This pattern rule has two targets:
9144 rule that has multiple targets (@pxref{Pattern Intro, ,Introduction to
9280 archive member name. This makes sense only for archive member targets
9467 commands are used for all targets and prerequisites that have no commands
9483 You can instead define commands to be used for targets for which there
9486 commands are used for all prerequisites which do not appear as targets in
9638 Make a list of all the pattern rules one of whose targets matches
9722 * Archive Members:: Archive members as targets.
9723 * Archive Update:: The implicit rule for archive member targets.
9731 @cindex archive member targets
9742 This construct is available only in targets and prerequisites, not in
9755 In fact, nearly all archive member targets are updated in just this way
10108 Declare phony targets with the special target @code{.PHONY}.
10243 @emph{all} targets, not just those without commands. This means you can
10636 The targets given to @code{make} on the command line. Setting this
10729 @item No targets specified and no makefile found. Stop.
10730 @itemx No targets. Stop.
10731 The former means that you didn't provide any targets to be built on the
10845 In addition, there are targets @code{shar} and @code{dist} that create