Lines Matching full:targets

20 and a list of targets to build and returns which targets are affected by
73 output to match the list of targets.
99   targets affected by the patch, so that we don't blame or punish the
108    those are mapped onto build targets. For some kinds of tests (like
116    and forth between test steps and build targets. That mapping
120 3. We might also want to know when test targets are affected by data files
124 4. We also want to ensure that particular targets still compile even if they
126    targets that don't yet have good test coverage. We might want to use meta
127    targets for this purpose as well.
129 5. However, for some meta targets, we don't necessarily want to rebuild the
135    targets.  In other words, some meta targets are *prunable*.
150 The interaction between 2) and 5) means that we need to treat meta targets
151 two different ways, and so we need to know which targets should be
152 pruned in the sense of 5) and which targets should be returned unchanged
158 * `test_targets`: the list of ninja targets which, if affected by a patch,
160   tests to run. Any meta targets in this list should *not* be pruned.
161 * `additional_compile_targets`: the list of ninja targets we wish to compile
162   *in addition to* the list in `test_targets`. Any meta targets
164   meta targets because they aren't mapped back to tests, and we don't want
169 * `compile_targets`, which is a list of pruned targets to be
171   pruned targets by a meta target if it turns out that all of the
175 * `test_targets`, which is a list of unpruned targets to be mapped
192 There may be targets listed in the input that don't exist in the build
194 and so we should return which targets are missing so the caller can
209   addition to the test targets.
216 build, or that there were no affected test targets as appropriate.
221 actually want to build every out of date target, only the targets
244   `wtf_unittests`, and `webkit_tests` and represents all of the targets
257 compile any additional targets.