Searched refs:GYP (Results 1 – 19 of 19) sorted by relevance
/external/webrtc/tools_webrtc/mb/docs/ |
D | design_spec.md | 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. [all …]
|
D | user_guide.md | 7 `mb` is a simple python wrapper around the GYP and GN meta-build tools to 8 be used as part of the GYP->GN migration. 48 (GN: group, GYP: none) target like 'blink_tests' or 98 `mb audit` is used to track the progress of the GYP->GN migration. You can 105 `mb gen` is responsible for generating the Ninja files by invoking either GYP 107 a directory, then runs GYP or GN as appropriate: 136 incorporated into the appropriate flags for GYP or GN as needed. 138 If gen ends up using GYP, the path must have a valid GYP configuration as the 174 in a GN build (in a GYP build, this is done as part of the compile step). 228 the environment and passed to GYP.
|
/external/webrtc/tools_webrtc/mb/ |
D | README.md | 4 GYP or GN, such that users and bots can call one script and not need to 5 worry about whether a given bot is meant to use GN or GYP.
|
/external/angle/infra/specs/ |
D | gn_isolate_map.pyl | 16 # they are referred to in GN or GYP specifically (the GYP target name is pretty 17 # much always the same as the Ninja target name, since GYP target names are not
|
/external/google-breakpad/ |
D | .gitignore | 70 # Ignore GYP generated Visual Studio artifacts. 78 # Ignore GYP generated Makefiles
|
D | DEPS | 46 # GYP project generator. 68 # TODO(chrisha): Fix the GYP files so that they work without
|
/external/skia/site/docs/dev/chrome/ |
D | commandbuffer.md | 14 the command buffer as a shared library and thus no GYP/GN flags are
|
/external/skqp/site/dev/chrome/ |
D | commandbuffer.md | 9 the command buffer as a shared library and thus no GYP/GN flags are
|
/external/libyuv/files/ |
D | libyuv.gyp | 21 # Can be enabled if your jpeg has GYP support.
|
D | libyuv_test.gyp | 11 # Can be enabled if your jpeg has GYP support.
|
/external/grpc-grpc/templates/ |
D | grpc.gyp.template | 3 # GRPC GYP build file
|
/external/boringssl/src/util/ |
D | generate_build_files.py | 386 class GYP(object): class 972 'gyp': GYP,
|
/external/pdfium/testing/ |
D | test.gni | 118 # target (post-GYP).
|
/external/boringssl/src/ |
D | INCORPORATING.md | 39 different projects use [GYP](https://gyp.gsrc.io/),
|
/external/google-breakpad/src/build/ |
D | common.gypi | 34 # Variables expected to be overriden on the GYP command line (-D) or by
|
/external/rust/crates/grpcio-sys/grpc/ |
D | grpc.gyp | 1 # GRPC GYP build file
|
/external/grpc-grpc/ |
D | grpc.gyp | 1 # GRPC GYP build file
|
/external/cldr/tools/java/org/unicode/cldr/util/data/external/ |
D | 2013-1_UNLOCODE_CodeListPart3.csv | 16036 ,"US","GYP","Greeley","Greeley","PA","--3--6--","RL","0401",,"4125N 07459W",
|
D | 2013-1_UNLOCODE_CodeListPart1.csv | 2601 ,"AU","GYP","Gympie","Gympie","QLD","---4----","AI","9912",,,
|