Lines Matching refs:GYP

7 MB is intended to address two major aspects of the GYP -> GN transition
11    back and forth between GN and GYP.
29 possible to GN or GYP. It should live as a very simple Python wrapper
44 with spaces and passed to GYP, or a dict that will be similarly converted),
46 'mb_type' field that says whether to use GN or GYP. Bot config files
50 `//tools/mb/mb_config.pyl` config file to determine whether to use GYP or GN
113    target (a GN group or a GYP 'none' target like `webkit_tests`) that
114    depends on the right list of files. Because the GN and GYP files know
117    is *not* currently available to MB (or GN or GYP), and so we have to 
122    There's no good way to do this in GYP, but GN supports this.
140    GYP and GN Ninja generators provide an 'all' target that captures (nearly,
142    neither GN nor GYP actually represents 'all' as a meta target in the build
219 `all` to Ninja (at least given how GN and GYP work); however, we
228 empty file list case, above, or an internal error in MB/GYP/GN). The
353 configurations to know whether to use GYP or GN, and which flags to
376 that GYP and GN already have to support anyway; in particular, it might
377 require MB to know how to parse GYP and GN values. The belief is that
389 use for GYP at all. We may revisit how this works once we encourage more
413 * MB is not intended to replace direct invocation of GN or GYP for
420   the GYP->GN migration is done, and so we should not add things for