Searched refs:GYP (Results 1 – 25 of 35) sorted by relevance
12
/external/v8/tools/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 or even the 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 189 in a GN build (in a GYP build, this is done as part of the compile step). 243 the environment and passed to GYP.
|
/external/v8/tools/v8.xcodeproj/ |
D | README.txt | 2 is needed for building on a Mac there is the option of using GYP to 7 Generating Xcode projects using GYP is how the Chromium
|
/external/v8/tools/visual_studio/ |
D | README.txt | 3 Studio project/solution is needed there is the option of using GYP to 8 Generating Visual Studio projects using GYP is how the Chromium
|
/external/v8/gypfiles/ |
D | isolate.gypi | 31 # property of the .isolate format. This permits to define GYP variables but is 32 # a stricter format than GYP so isolate.py can read it. 62 # like '0' or '1', aren't stripped out by GYP. Run 'isolate.py help'
|
/external/v8/tools/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/webrtc/webrtc/test/ |
D | metrics.gyp | 15 # The metrics code must be kept in its own GYP file in order to 18 # GYP generation would occur, because the libyuv.gypi unittest target
|
/external/webrtc/webrtc/build/ |
D | isolate.gypi | 47 # property of the .isolate format. This permits to define GYP variables but is 48 # a stricter format than GYP so isolate.py can read it. 76 # like '0' or '1', aren't stripped out by GYP. Run 'isolate.py help' for
|
/external/webrtc/talk/build/ |
D | isolate.gypi | 65 # property of the .isolate format. This permits to define GYP variables but is 66 # a stricter format than GYP so isolate.py can read it. 94 # like '0' or '1', aren't stripped out by GYP. Run 'isolate.py help' for
|
/external/google-breakpad/ |
D | DEPS | 48 # GYP project generator. 58 # TODO(chrisha): Fix the GYP files so that they work without
|
D | .gitignore | 29 # Ignore GYP generated Visual Studio artifacts.
|
/external/webrtc/tools/gritsettings/ |
D | README | 5 build/apk_test.gypi GYP file and depend on the
|
/external/v8/gypfiles/mac/ |
D | asan.gyp | 15 # Path is relative to this GYP file.
|
/external/skia/site/dev/chrome/ |
D | commandbuffer.md | 9 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/pdfium/ |
D | DEPS | 108 # TODO(GYP): Remove this when no tools rely on GYP anymore.
|
/external/webrtc/webrtc/examples/androidapp/ |
D | README | 5 - Set up webrtc-related GYP variables:
|
/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 | 331 class GYP(object): class 714 platforms.append(GYP())
|
/external/webrtc/ |
D | DEPS | 110 # A change to a .gyp, .gypi, or to GYP itself should run the generator.
|
/external/pdfium/testing/ |
D | test.gni | 121 # target (post-GYP).
|
/external/v8/ |
D | snapshot_toolchain.gni | 48 # TODO(GYP): Currently only regular (non-cross) compiles, and cross-compiles
|
/external/boringssl/src/ |
D | INCORPORATING.md | 39 different projects use [GYP](https://gyp.gsrc.io/),
|
12