| /external/perfetto/ |
| D | BUILD | 46 # GN target: //src/ipc/protoc_plugin:ipc_plugin
57 # GN target: //src/ipc:perfetto_ipc
79 # GN target: //src/protozero/protoc_plugin:cppgen_plugin
90 # GN target: //src/protozero/protoc_plugin:protozero_plugin
101 # GN target: //src/protozero:protozero
127 # GN target: //test:client_api_example
172 # GN target: //:libperfetto
275 # GN target: //include/perfetto/base:base
294 # GN target: //include/perfetto/ext/base:base
339 # GN target: //include/perfetto/ext/ipc:ipc
[all …]
|
| D | Android.bp | 17 // GN: //src/profiling/memory:heapprofd
164 // GN: //src/profiling/memory:heapprofd_api_noop
185 // GN: //src/profiling/memory:heapprofd_client
218 // GN: //src/profiling/memory:heapprofd_client_api
269 // GN: //src/profiling/memory:heapprofd_standalone_client
426 // GN: //src/ipc/protoc_plugin:ipc_plugin
450 // GN: //:libperfetto
617 // GN: //src/android_internal:libperfetto_android_internal
660 // GN: //:libperfetto_client_experimental
855 // GN: //src/perfetto_cmd:perfetto
[all …]
|
| /external/llvm-project/llvm/utils/gn/ |
| D | README.rst | 2 Building LLVM with GN
13 *Warning* The GN build is experimental and best-effort. It might not work,
17 to update GN build files. Reviewers should not ask authors to update GN build
18 files. Keeping the GN build files up-to-date is on the people who use the GN
21 `GN <https://gn.googlesource.com/gn/>`_ is a metabuild system. It always
25 The main motivation behind the GN build is that some people find it more
27 just parts of LLVM, and embedding the LLVM GN build from other builds are
28 non-goals for the GN build.
30 This is a `good overview of GN <https://docs.google.com/presentation/d/15Zwb53JcncHfEwHpnG_PoIbbzQ3…
45 #. ``llvm/utils/gn/gn.py gen out/gn`` to run GN and create build files.
[all …]
|
| D | .gn | 11 # The normal GN setup is to have BUILD.gn files in-tree and a root BUILD.gn
12 # file. Since LLVM's GN build is unofficial, set secondary_source to tell GN
|
| /external/pigweed/docs/ |
| D | build_system.rst | 154 Of the supported build systems, GN is the most full-featured, followed by CMake,
171 GN section in Pigweed's build systems
173 A perhaps unfamiliar name, `GN (Generate Ninja)`_ is a meta-build system that
175 first experimented with GN after hearing about it from another team, and we
176 quickly came to appreciate its speed and simplicity. GN has become Pigweed's
185 The GN build argument
187 This section describes Pigweed's GN build structure, how it is used upstream,
189 containing some details about how GN works in general, this section is not
190 intended to be a guide on how to use GN. To learn more about the tool itself,
191 refer to the official `GN reference`_.
[all …]
|
| D | targets.rst | 7 Pigweed's GN build comes with an extensible target system that allows it to be
12 Each Pigweed target built by a project is defined within the GN build as a
15 In Pigweed, these target toolchains are defined as GN scopes, which are fed into
16 a ``generate_toolchain`` template to create the complete GN toolchain.
55 scope in its toolchain. Every variable in this scope is an override of a GN
58 * ``default_configs``: A list of GN configs to apply to every ``pw_*`` GN
61 * ``default_public_deps``: List of GN targets which are added as a dependency
62 to all ``pw_*`` GN targets. This is used to add global module dependencies;
104 # Create the actual GN toolchain from the scope.
|
| D | python_build.rst | 6 Pigweed uses a custom GN-based build system to manage its Python code. The
12 Pigweed's Python code is exclusively managed by GN, but the GN-based build may
14 setup uses GN to set up the initial Python environment, regardless of the final
15 build system. As needed, non-GN projects can declare just their Python packages
16 in GN.
150 Pigweed uses GN as its primary build system for all languages. While GN does not
151 natively support Python, adding support is straightforward with GN templates.
153 GN has strong multi-toolchain and multi-language capabilities. In GN, it is
156 declaration. When using GN for multiple languages, Ninja schedules build steps
159 Not all Pigweed users build with GN. Of Pigweed's three supported build systems,
[all …]
|
| D | getting_started.md | 36 (3) Configure the GN build.
172 Pigweed's primary build system is GN/Ninja based. There are CMake and Bazel
174 with the GN build. We strongly recommend you stick to the GN build system.
176 GN (Generate Ninja) just does what it says on the tin; GN generates
179 The default GN configuration generates build files that allow you to build host
183 Run GN as seen below:
191 run GN again; just rebuild using Ninja directly.
228 Running tests as part of the build isn't particularly expensive because GN
293 ### 3. Configure GN
295 We can tell GN to use the testing server by enabling a build arg specific to
[all …]
|
| /external/webrtc/ |
| D | native-api.md | 82 `WEBRTC_EXCLUDE_BUILT_IN_SSL_ROOT_CERTS`. If you use GN, you can just set the GN
83 argument `rtc_builtin_ssl_root_certificates` to false and GN will define the
92 `WEBRTC_EXCLUDE_FIELD_TRIAL_DEFAULT`. If you use GN, you can just set the GN
93 argument `rtc_exclude_field_trial_default` to true and GN will define the
104 `WEBRTC_EXCLUDE_METRICS_DEFAULT`. If you use GN, you can just set the GN
105 argument `rtc_exclude_metrics_default` to true and GN will define the
114 `WEBRTC_EXCLUDE_TRANSIENT_SUPPRESSOR`. If you use GN, you can just set the GN
115 argument `rtc_exclude_transient_suppressor` to true and GN will define the macro
|
| /external/skqp/site/user/ |
| D | build.md | 7 Skia uses [GN](https://chromium.googlesource.com/chromium/src/tools/gn/) to
27 by a GN argument that looks something like `skia_use_foo` for appropriate
51 Run GN to generate your build files.
60 GN allows fine-grained settings for developers and special situations.
99 When generating your GN build files, pass the path to your `ndk` and your
142 Once those files are in place, generate the GN args that resemble the following:
217 Run GN to generate your build files. Set `target_os="ios"` to build for iOS.
248 If GN is unable to locate either of those, it will print an error message. In that
249 case, you can pass your `VC` path to GN via `win_vc`.
258 You can then pass the VC and SDK paths to GN by setting your GN args:
[all …]
|
| /external/pigweed/pw_build/ |
| D | docs.rst | 8 multiple build systems. Our personal favorite is `GN`_/`Ninja`_, which is used
18 Beyond just compiling code, Pigweed’s GN build system can also:
25 These are only supported in the GN build, so we recommend using it if possible.
27 GN / Ninja
29 The GN / Ninja build system is the primary build system used for upstream
37 ``pw_build`` also provides several useful GN templates that are used throughout
50 Pigweed defines wrappers around the four basic GN binary types ``source_set``,
77 GN templates for :ref:`Python build automation <docs-python-build>` are
89 In their simplest form, a :ref:`facade<docs-module-structure-facades>` is a GN
95 else a GN ``source_set`` provides.
[all …]
|
| D | python.rst | 4 Python GN templates
6 The Python build is implemented with GN templates defined in
24 GN permits using abbreviated labels when the target name matches the directory
50 - ``python_deps`` - Dependencies on other pw_python_packages in the GN build.
52 - ``other_deps`` - Dependencies on GN targets that are not pw_python_packages.
105 traversing the ``pw_python_package_wheels`` `GN metadata
|
| D | python_action.gni | 19 # This wraps a regular Python script GN action with an invocation of a script-
21 # actions as GN's action(), with the following additions or changes:
44 # in GN. These include the following:
47 # output file (such as a .a or .elf) from a GN target
51 # object files produced by the provided GN target
57 # GN root directory relative to the build directory (in which the runner
|
| /external/llvm-project/llvm/unittests/Transforms/Utils/ |
| D | FunctionComparatorTest.cpp | 48 GlobalNumberState *GN) in TestComparator() argument
49 : FunctionComparator(F1, F2, GN) { in TestComparator()
114 GlobalNumberState GN; in TEST() local
115 TestComparator Cmp(F1.F, F2.F, &GN); in TEST()
|
| /external/skia/site/docs/user/ |
| D | build.md | 11 Skia uses [GN](https://chromium.googlesource.com/chromium/src/tools/gn/) to
41 a GN argument that looks something like `skia_use_foo` for appropriate `foo`.
64 `--args='cc="clang-6.0" cxx="clang++6.0"'` GN build arguments, as illustrated in
97 GN allows multiple build folders to coexist; each build can be configured
142 When generating your GN build files, pass the path to your `ndk` and your
193 Once those files are in place, generate the GN args that resemble the following:
271 Run GN to generate your build files. Set `target_os="ios"` to build for iOS.
282 set the GN args `skia_ios_identity` to match your code signing identity and
321 Skia can build on Windows with Visual Studio 2017 or 2019. If GN is unable to
323 pass your `VC` path to GN via `win_vc`.
[all …]
|
| /external/skqp/site/user/special/ |
| D | lua.md | 16 To build Lua support into Skia tools, set the GN argument `skia_use_lua` to `true`.
17 Optionally, set `skia_use_system_lua`. Then re-run GN.
31 This feature is not yet supported by GN, but would have looked something like this:
|
| /external/pigweed/pw_toolchain/ |
| D | generate_toolchain.gni | 46 # trigger this toolchain to be generated. GN only allows one toolchain to
51 # defaults: (required) A scope setting GN build arg values to apply to GN
54 # The defaults scope should contain values for builtin GN arguments:
278 # express such graphs in terms that GN understands, this is the
329 # GN-ism: GN gets mad if you directly forward the contents of
336 # GN-ism: GN gets mad if you directly forward the contents of
344 # pw_toolchain_defaults: A scope setting defaults to apply to GN targets
|
| /external/angle/third_party/vulkan-deps/glslang/ |
| D | README.chromium | 14 Ported build rules from CMake to GN.
15 5/13/2016 - Updated GN build rules to include new files added in repository.
|
| /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
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
71 It implements the equivalent functionality in GN by calling `gn refs
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 …]
|
| /external/llvm-project/llvm/utils/gn/docs/ |
| D | deterministic.md | 1 Deterministic builds with LLVM's GN build
9 with the GN build. It requires some configuration though.
|
| /external/perfetto/docs/contributing/ |
| D | build-instructions.md | 119 on [GN][gn-quickstart].
120 The Android build file ([Android.bp](/Android.bp)) is autogenerated from the GN
122 change touches GN files or introduces new ones.
124 A presubmit check checks that the Android.bp is consistent with GN files when
150 and GN. Windows is supported only for a subset of the targets (mainly
160 The following [GN args][gn-quickstart] are supported:
254 In case of cross-compilation, the GN variables have the following semantic:
286 `extra_xxxflags` GN variables as follows. The extra flags are always appended
287 (hence, take precedence) to the set of flags that the GN build files generate.
|
| /external/llvm-project/llvm/lib/Target/Hexagon/ |
| D | HexagonCommonGEP.cpp | 201 friend raw_ostream &operator<< (raw_ostream &OS, const GepNode &GN);
210 raw_ostream &operator<< (raw_ostream &OS, const GepNode &GN) { in operator <<() argument
213 if (GN.Flags & GepNode::Root) { in operator <<()
217 if (GN.Flags & GepNode::Internal) { in operator <<()
223 if (GN.Flags & GepNode::Used) { in operator <<()
228 if (GN.Flags & GepNode::InBounds) { in operator <<()
234 if (GN.Flags & GepNode::Root) in operator <<()
235 OS << "BaseVal:" << GN.BaseVal->getName() << '(' << GN.BaseVal << ')'; in operator <<()
237 OS << "Parent:" << GN.Parent; in operator <<()
240 if (ConstantInt *CI = dyn_cast<ConstantInt>(GN.Idx)) in operator <<()
[all …]
|
| /external/swiftshader/third_party/llvm-10.0/llvm/lib/Target/Hexagon/ |
| D | HexagonCommonGEP.cpp | 201 friend raw_ostream &operator<< (raw_ostream &OS, const GepNode &GN);
220 raw_ostream &operator<< (raw_ostream &OS, const GepNode &GN) { in operator <<() argument
223 if (GN.Flags & GepNode::Root) { in operator <<()
227 if (GN.Flags & GepNode::Internal) { in operator <<()
233 if (GN.Flags & GepNode::Used) { in operator <<()
238 if (GN.Flags & GepNode::InBounds) { in operator <<()
244 if (GN.Flags & GepNode::Root) in operator <<()
245 OS << "BaseVal:" << GN.BaseVal->getName() << '(' << GN.BaseVal << ')'; in operator <<()
247 OS << "Parent:" << GN.Parent; in operator <<()
250 if (ConstantInt *CI = dyn_cast<ConstantInt>(GN.Idx)) in operator <<()
[all …]
|
| /external/pigweed/pw_malloc/ |
| D | docs.rst | 23 2. If using GN build, Specify the ``pw_sys_io_BACKEND`` GN build arg to point
|
| /external/swiftshader/src/Vulkan/ |
| D | vulkan.gni | 15 # File containing GN "constants" for Swiftshader Vulkan so that GN-based
|