Lines Matching refs:targets
132 or prerequisites to mark other targets
137 * Multiple Targets:: When to make use of several targets in a rule.
139 * Static Pattern:: Static pattern rules apply to multiple targets
218 to a group of targets that match a pattern.
291 * Archive Members:: Archive members as targets.
292 * Archive Update:: The implicit rule for archive member targets.
465 program; examples of targets are executable or object files. A target
484 are the targets of the particular rule. `make' carries out the
546 In the example makefile, the targets include the executable file
575 called "phony targets". *Note Phony Targets::, for information about
585 By default, `make' starts with the first target (not targets whose
587 are the targets that `make' strives ultimately to update. You can
609 The other rules are processed because their targets appear as
617 the targets of any rules--so `make' does nothing for these files. But
747 you group entries by their prerequisites instead of by their targets.
841 called the rule's "targets". It lists the other files that the
842 targets depend on, called the "prerequisites" of the target, and
843 may also give commands to use to create or update the targets.
1087 Sets the default goal to be used if no targets were specified on
1215 which are specified as targets of a double-colon rule with commands but
1235 use an out-of-date makefile to decide which targets to touch. So the
1240 other targets. Thus, `make -f mfile -n foo' will update `mfile', read
1265 one in the other, and add more targets or variable definitions.
1276 to make the target `foo' (and other targets), you can write a makefile
1311 rules, and constructs a dependency graph of all the targets and their
1313 structures to determine what targets will need to be rebuilt and to
1384 some or all targets defined in the makefile. In order for this second
1391 prerequisites of the targets defined after the special target are
1451 `main' and `lib' targets will be `$($@_OBJS)'. During the secondary
1560 certain files, called the rule's "targets" (most often only one per
1567 rule in the first makefile. If the first rule has multiple targets,
1588 or prerequisites to mark other targets
1593 * Multiple Targets:: When to make use of several targets in a rule.
1595 * Static Pattern:: Static pattern rules apply to multiple targets
1672 A rule tells `make' two things: when the targets are out of date,
1745 Wildcard expansion is performed by `make' automatically in targets
1926 prerequisites and targets of rules.
2235 Since it knows that phony targets do not name actual files that
2237 for phony targets (*note Implicit Rules::). This is why declaring a
2248 Another example of the usefulness of phony targets is in conjunction
2268 advantage of `make''s ability to build targets in parallel (*note
2271 By declaring the subdirectories as phony targets (you must do this as
2298 Phony targets can have prerequisites. When one directory contains
2345 updated whenever its rule is run. This implies that all targets
2403 Certain names have special meanings if they appear as targets.
2407 be phony targets. When it is time to consider such a target,
2426 The targets which `.PRECIOUS' depends on are given the following
2441 The targets which `.INTERMEDIATE' depends on are treated as
2446 The targets which `.SECONDARY' depends on are treated as
2450 `.SECONDARY' with no prerequisites causes all targets to be treated
2540 such as `.c.o'. These targets are suffix rules, an obsolete way of
2553 A rule with multiple targets is equivalent to writing many rules, each
2555 apply to all the targets, but their effects may vary because you can
2557 rule contributes the same prerequisites to all the targets also.
2568 * Similar commands work for all the targets. The commands do not
2590 cannot do this with multiple targets in an ordinary rule, but you can
2651 "Static pattern rules" are rules which specify multiple targets and
2653 name. They are more general than ordinary rules with multiple targets
2654 because the targets do not have to have identical prerequisites. Their
2674 The TARGETS list specifies the targets that the rule applies to. The
2675 targets can contain wildcard characters, just like the targets of
2689 pattern `%.o', with `foo' as the stem. The targets `foo.c' and
2697 is the same for all targets.
2770 targets that you specify in the rule. It cannot apply to any other
2771 target and it invariably does apply to each of the targets specified.
2786 rule applies to precisely the targets specified.
2809 individually, just as rules with different targets are processed.
3103 commands for targets which are not rebuilt are never expanded.
3405 further commands will be executed for these targets, since their
3411 pending targets, remaking them if necessary, before it gives up and
3418 targets up to date; once `make' learns that this is impossible, it
3492 it useful to declare targets that invoke recursive `make' commands as
3544 option marks targets as up to date without actually running any
3832 When the same sequence of commands is useful in making various targets,
3834 refer to the canned sequence from the rules for those targets. The
3923 You may be inclined to define empty command strings for targets that
3938 explicit request into targets, prerequisites, commands, and other parts
3990 to a group of targets that match a pattern.
4004 Variable references can be used in any context: targets,
4763 multiple targets, and each of those targets has a different value for
4767 ignore the target-specific values from any other targets.
4804 will assign `CFLAGS' the value of `-O' for all targets matching the
5791 targets, implicit or explicit rules, etc.
6116 The "goals" are the targets that `make' should strive ultimately to
6117 update. Other targets are updated as well if they appear as
6121 counting targets that start with a period). Therefore, makefiles are
6124 has several targets, only the first target in the rule becomes the
6136 a switch or variable definition, respectively). Even targets not in
6182 Make all the top-level targets the makefile knows about.
6196 Any of these targets might be defined to delete _more_ files than
6234 and how to update each target. But updating the targets is not always
6242 make the targets up to date, but not actually execute them.
6246 "Touch". The activity is to mark the targets as up to date without
6248 the targets but does not really change their contents.
6253 targets are up to date already; but execute no commands in either
6276 but the exit status code it returns is zero if and only if the targets
6419 the pending targets, remaking them if necessary, before it gives up and
6452 Consider all targets out-of-date. GNU `make' proceeds to consider
6453 targets and their prerequisites using the normal algorithms;
6454 however, all targets so considered are always remade regardless of
6554 prerequisites of these targets can be processed all the same.
6605 return an exit status that is zero if the specified targets are