| /external/angle/third_party/OpenCL-CTS/ |
| D | BUILD.gn | 9 "$angle_root/third_party/OpenCL-CTS/gn/SVM:test_svm",
10 "$angle_root/third_party/OpenCL-CTS/gn/allocations:test_allocations",
11 "$angle_root/third_party/OpenCL-CTS/gn/api:test_api",
12 "$angle_root/third_party/OpenCL-CTS/gn/atomics:test_atomics",
13 "$angle_root/third_party/OpenCL-CTS/gn/basic:test_basic",
14 "$angle_root/third_party/OpenCL-CTS/gn/buffers:test_buffers",
15 "$angle_root/third_party/OpenCL-CTS/gn/c11_atomics:test_c11_atomics",
16 "$angle_root/third_party/OpenCL-CTS/gn/commonfns:test_commonfns",
17 "$angle_root/third_party/OpenCL-CTS/gn/compiler:test_compiler",
18 "$angle_root/third_party/OpenCL-CTS/gn/computeinfo:test_computeinfo",
[all …]
|
| /external/skia/site/docs/user/ |
| D | build.md | 11 Skia uses [GN](https://chromium.googlesource.com/chromium/src/tools/gn/) to
30 a GN argument that looks something like `skia_use_foo` for appropriate `foo`.
53 `--args='cc="clang" cxx="clang++"'` GN build arguments, as illustrated in
57 If you do not specify `cc` and `cxx` in your gn arguments, Skia will default to
62 Run `gn gen` to generate your build files. As arguments to `gn gen`, pass a name
68 bin/gn gen out/Static --args='is_official_build=true'
74 bin/gn gen out/Shared --args='is_official_build=true is_component_build=true'
77 If you find that you don't have `bin/gn`, make sure you've run:
83 For a list of available build arguments, take a look at `gn/skia.gni`, or run:
86 bin/gn args out/Debug --list
[all …]
|
| /external/pigweed/pw_build/py/pw_build/ |
| D | gn_utils.py | 14 """Utilities for manipulating GN labels and paths."""
24 """Raised when creating a GN object fails."""
28 """Represents a GN source path to a file in the source tree."""
34 gn: str | None = None, # pylint: disable=invalid-name
36 """Creates a GN source path.
39 base: A base GN source path. Other parameters are used to define
42 gn: A GN source path relative to `base`.
48 elif gn:
49 self._from_gn(base_path, gn)
73 """Populates this object using a GN label.
[all …]
|
| D | gn_writer.py | 14 """Writes a formatted BUILD.gn _file."""
47 """Represents a partial BUILD.gn file being constructed.
50 object wraps this one, and ensures that the GN file produced includes the
69 """Adds a GN comment.
86 """Adds a GN import.
89 gni: The source-relative path to a GN import file.
96 """Adds a list of GN imports.
99 imports: A list of GN import files.
105 """Adds a GN config.
108 config: The GN config data to write.
[all …]
|
| /external/mesa3d/.gitlab-ci/container/patches/ |
| D | build-skqp_fetch_gn.patch | 1 diff --git a/bin/fetch-gn b/bin/fetch-gn
3 --- a/bin/fetch-gn
4 +++ b/bin/fetch-gn
26 -dst = 'bin/gn.exe' if 'win32' in sys.platform else 'bin/gn'
27 +gnzip = os.path.join(tempfile.mkdtemp(), 'gn.zip')
36 + url = 'https://chrome-infra-packages.appspot.com/dl/gn/gn/{}-{}/+/git_revision:{}'.format(
46 +gn = 'gn.exe' if 'win32' in sys.platform else 'gn'
48 + f.extract(gn, 'bin')
52 - f.write(urllib2.urlopen('https://chromium-gn.storage-download.googleapis.com/' + sha1).read())
53 +gn = os.path.join('bin', gn)
[all …]
|
| /external/openthread/script/ |
| D | check-gn-build | 39 # Check GN build for OT1.1
40 rm gn-out -r || true
41 gn gen --check gn-out
42 gn args gn-out --list
43 ninja -C gn-out
44 test -f gn-out/obj/src/core/libopenthread-ftd.a
46 # Check GN build for OT1.3
47 rm gn-out -r || true
48 mkdir gn-out
49 echo 'openthread_config_thread_version = "1.3"' >gn-out/args.gn
[all …]
|
| /external/angle/third_party/clspv/gn/ |
| D | README.md | 1 # CLSPV GN Build
3 The clspv official build system is CMake and as such have no GN build infra. The
4 files in here enable building `clspv` using the ANGLE GN build infra.
6 The top-level build file is `BUILD.gn` with all the auxiliary build files
7 located in the `gn` folder. The `clspv` build is heavily dependent on the LLVM
9 `gn/llvm` location. These utilize the LLVM experimental GN build infra [1].
13 The GN build in here is setup to function within the ANGLE GN build
17 Add the following to `args.gn` file
28 The LLVM targets required for clspv are housed in the `gn/llvm` location. In the
30 target sources needs to be modified in `gn/llvm/sources/BUILD.gn`.
[all …]
|
| /external/perfetto/src/profiling/memory/ |
| D | BUILD.gn | 15 import("../../../gn/fuzzer.gni")
16 import("../../../gn/perfetto.gni")
17 import("../../../gn/test.gni")
25 "../../../gn:default_deps",
32 "../../../gn:default_deps",
51 # single bp target). However this is not correctly reflected in the gn
58 configs -= [ "//gn/standalone:android_liblog" ] # nogncheck
72 "../../../gn:default_deps",
86 "../../../gn:default_deps",
96 "../../../gn:default_deps",
[all …]
|
| /external/skia/bazel/external/gn/ |
| D | BUILD.bazel | 1 # This is a convenience wrapper to run a platform-specific version of GN with any provided flags
3 # exact flavor of GN needed and use --run_under to change directories before running GN.
6 # bazelisk //bazel/external/gn -- format gn/sksl.gni
8 # gn format gn/sksl.gni
9 # except it uses a hermetic version of gn instead of whatever is on the user's machine. Note the --
10 # to pass arguments to gn and not have Bazel try to understand them.
12 name = "gn",
13 srcs = [":gn.py"],
27 # We need to get the absolute path here because we want to run gn from the
35 # Pass any other args along to GN, and stream any output to the user.
[all …]
|
| /external/perfetto/ |
| D | BUILD | 53 # GN target: //src/base:perfetto_base_default_platform
68 # GN target: //src/ipc/protoc_plugin:ipc_plugin
79 # GN target: //src/ipc:perfetto_ipc
104 # GN target: //src/protozero/protoc_plugin:cppgen_plugin
115 # GN target: //src/protozero/protoc_plugin:protozero_plugin
126 # GN target: //src/protozero:protozero
155 # GN target: //src/tools/proto_filter:proto_filter
193 # GN target: //src/tools/proto_merger:proto_merger
213 # GN target: //src/trace_processor/rpc:trace_processor_rpc
376 # GN target: //test:client_api_example
[all …]
|
| /external/perfetto/gn/standalone/ |
| D | BUILDCONFIG.gn | 66 "//gn/standalone:default",
67 "//gn/standalone:extra_warnings",
68 "//gn/standalone:no_exceptions",
69 "//gn/standalone:no_rtti",
70 "//gn/standalone:visibility_hidden",
71 "//gn/standalone/libc++:config",
72 "//gn/standalone/sanitizers:sanitizers_cflags",
73 "//gn/standalone:c++17",
77 default_configs += [ "//gn/standalone:debug_noopt" ]
79 default_configs += [ "//gn/standalone:release" ]
[all …]
|
| /external/skia/bin/ |
| D | fetch-gn | 20 gnzip = os.path.join(tempfile.mkdtemp(), 'gn.zip')
26 url = 'https://chrome-infra-packages.appspot.com/dl/gn/gn/{}-{}/+/git_revision:{}'.format(
30 gn = 'gn.exe' if 'win32' in sys.platform else 'gn' variable
32 f.extract(gn, 'bin')
34 gn = os.path.join('bin', gn) variable
36 os.chmod(gn, stat.S_IRUSR | stat.S_IWUSR | stat.S_IXUSR |
40 # We'll also copy to a path that depot_tools' GN wrapper will expect to find the binary.
41 copy_path = 'buildtools/linux64/gn' if 'linux' in sys.platform else \
42 'buildtools/mac/gn' if 'darwin' in sys.platform else \
43 'buildtools/win/gn.exe'
[all …]
|
| /external/cronet/base/allocator/partition_allocator/ |
| D | build_config.md | 5 [GN args][gn-declare-args], which propagate via
11 * [`//base/allocator/partition_allocator/BUILD.gn`][pa-build-gn],
12 * Everything else ending in `.gn` or `.gni` in
15 * [`//base/allocator/BUILD.gn`][base-allocator-build-gn], and
16 * [`//base/BUILD.gn`][base-build-gn].
34 ## Select GN Args
45 it was logically identical to wholly disabling it in Chromium. This GN
90 Over time, the above list should evolve into a list of macros / GN args
94 [gn-declare-args]: https://gn.googlesource.com/gn/+/refs/heads/main/docs/reference.md#func_declare_…
96 [pa-build-gn]: https://source.chromium.org/chromium/chromium/src/+/main:base/allocator/partition_al…
[all …]
|
| /external/pigweed/docs/ |
| D | build_system.rst | 154 Of the supported build systems, GN is the most full-featured, followed by CMake,
158 A quick note on terminology: the word "target" is overloaded within GN/Bazel (and
159 Pigweed)---it can refer to either a GN/Bazel build target, such as a ``source_set``
163 To avoid confusing the two, we refer to the former as "GN/Bazel targets" and the
166 .. _docs-build-system-gn:
168 GN section in Pigweed's build systems
170 A perhaps unfamiliar name, `GN (Generate Ninja)`_ is a meta-build system that
172 first experimented with GN after hearing about it from another team, and we
173 quickly came to appreciate its speed and simplicity. GN has become Pigweed's
179 .. _GN (Generate Ninja): https://gn.googlesource.com/gn
[all …]
|
| D | python_build.rst | 4 Pigweed's GN Python Build
9 - :bdg-ref-primary-line:`module-pw_build` for other GN templates available
14 Pigweed uses a custom GN-based build system to manage its Python code. The
20 Pigweed's Python code is exclusively managed by GN, but the GN-based build may
22 setup uses GN to set up the initial Python environment, regardless of the final
23 build system. As needed, non-GN projects can declare just their Python packages
24 in GN.
28 In addition to compiler commands a Pigweed GN build will execute Python scripts
31 :ref:`module-pw_build-pw_python_action` GN template which will ultimately run
39 When a Pigweed GN build starts a single venv is created for use by all
[all …]
|
| /external/libchrome/build/ |
| D | clobber.py | 16 """Extracts from a build.ninja the commands to run GN.
18 The commands to run GN are the gn rule and build.ninja build step at the
19 top of the build.ninja file. We want to keep these when deleting GN builds
20 since we want to preserve the command-line flags to GN.
25 # Read until the third blank line. The first thing GN writes to the file
26 # is "ninja_required_version = x.y.z", then the "rule gn" and the third
51 # GN writes a build.ninja.d file. Note that not all GN builds have args.gn.
57 # GN builds aren't automatically regenerated when you sync. To avoid
58 # messing with the GN workflow, erase everything but the args file, and
59 # write a dummy build.ninja file that will automatically rerun GN the next
[all …]
|
| /external/cronet/build/ |
| D | clobber.py | 16 """Extracts from a build.ninja the commands to run GN.
18 The commands to run GN are the gn rule and build.ninja build step at the
19 top of the build.ninja file. We want to keep these when deleting GN builds
20 since we want to preserve the command-line flags to GN.
58 # GN writes a build.ninja.d file. Note that not all GN builds have args.gn.
64 # GN builds aren't automatically regenerated when you sync. To avoid
65 # messing with the GN workflow, erase everything but the args file, and
66 # write a dummy build.ninja file that will automatically rerun GN the next
72 gn_args_file = os.path.join(build_dir, 'args.gn')
81 # and we still want to restore args.gn/build.ninja/build.ninja.d, so catch
[all …]
|
| D | dotfile_settings.gni | 5 # This file contains variables that can be imported into a repo's dotfile (.gn)
12 "//build/config/compiler/BUILD.gn",
13 "//build/config/compiler/pgo/BUILD.gn",
18 "//build/config/linux/atk/BUILD.gn",
19 "//build/config/linux/atspi2/BUILD.gn",
20 "//build/config/linux/BUILD.gn",
21 "//build/config/linux/dri/BUILD.gn",
25 "//build/config/posix/BUILD.gn",
28 "//build/config/win/BUILD.gn",
33 "//build/toolchain/BUILD.gn",
[all …]
|
| /external/angle/build/ |
| D | clobber.py | 16 """Extracts from a build.ninja the commands to run GN.
18 The commands to run GN are the gn rule and build.ninja build step at the
19 top of the build.ninja file. We want to keep these when deleting GN builds
20 since we want to preserve the command-line flags to GN.
58 # GN writes a build.ninja.d file. Note that not all GN builds have args.gn.
64 # GN builds aren't automatically regenerated when you sync. To avoid
65 # messing with the GN workflow, erase everything but the args file, and
66 # write a dummy build.ninja file that will automatically rerun GN the next
72 gn_args_file = os.path.join(build_dir, 'args.gn')
81 # and we still want to restore args.gn/build.ninja/build.ninja.d, so catch
[all …]
|
| D | dotfile_settings.gni | 5 # This file contains variables that can be imported into a repo's dotfile (.gn)
12 "//build/config/compiler/BUILD.gn",
13 "//build/config/compiler/pgo/BUILD.gn",
18 "//build/config/linux/atk/BUILD.gn",
19 "//build/config/linux/atspi2/BUILD.gn",
20 "//build/config/linux/BUILD.gn",
21 "//build/config/linux/dri/BUILD.gn",
25 "//build/config/posix/BUILD.gn",
28 "//build/config/win/BUILD.gn",
33 "//build/toolchain/BUILD.gn",
[all …]
|
| /external/perfetto/src/trace_processor/ |
| D | BUILD.gn | 15 import("../../gn/fuzzer.gni")
16 import("../../gn/perfetto.gni")
17 import("../../gn/perfetto_cc_proto_descriptor.gni")
18 import("../../gn/perfetto_host_executable.gni")
19 import("../../gn/test.gni")
20 import("../../gn/wasm.gni")
39 "../../gn:default_deps",
56 "../../gn:default_deps",
72 "../../gn:default_deps",
93 "../../gn:default_deps",
[all …]
|
| /external/perfetto/src/trace_processor/util/ |
| D | BUILD.gn | 15 import("../../../gn/perfetto.gni")
16 import("../../../gn/perfetto_cc_proto_descriptor.gni")
28 "../../../gn:default_deps",
43 "../../../gn:default_deps",
54 "../../../gn:default_deps",
60 deps += [ "../../../gn:zlib" ]
70 "../../../gn:default_deps",
81 "../../../gn:default_deps",
95 "../../../gn:default_deps",
111 "../../../gn:default_deps",
[all …]
|
| /external/perfetto/src/protozero/filtering/ |
| D | BUILD.gn | 15 import("../../../gn/fuzzer.gni")
16 import("../../../gn/perfetto_host_executable.gni")
17 import("../../../gn/proto_library.gni")
18 import("../../../gn/test.gni")
30 "../../../gn:default_deps",
37 deps = [ "../../../gn:default_deps" ]
48 "../../../gn:default_deps",
61 "../../../gn:default_deps",
73 "../../../gn:default_deps",
88 "../../../gn:default_deps",
[all …]
|
| /external/webrtc/docs/native-code/ios/ |
| D | index.md | 25 for both Mac and iOS development, since GN allows you to generate your
45 [GN][gn] is used to generate [Ninja][ninja] project files. In order to configure
46 [GN][gn] to generate build files for iOS certain variables need to be set.
52 - To build for iOS this should be set as `target_os="ios"` in your `gn args`.
65 The [GN][gn] command for generating build files is `gn gen <output folder>`.
67 After you've generated your build files once, subsequent invocations of `gn gen`
69 To edit these at any time use `gn args <output folder>`. This will open up
71 changes and save the file, `gn` will regenerate your project files for you
78 $ gn gen out/ios_64 --args='target_os="ios" target_cpu="arm64"'
81 $ gn gen out/ios_sim --args='target_os="ios" target_cpu="x64"'
[all …]
|
| /external/pigweed/seed/ |
| D | 0111-build-systems.rst | 19 <https://bazel.build/>`_ as its primary build system, replacing `GN
20 <https://gn.googlesource.com/gn/>`_ in that role.
25 files for multiple systems (Bazel, CMake, GN, Soong), as well as other
35 Pigweed's primary build system has been GN, but soon will be Bazel.
40 GN has been Pigweed's primary build system since inception, and we've developed
41 an extensive GN build that was used to successfully ship products at scale. GN
45 But GN has limitations:
47 #. **Small community.** GN is a niche build system: the only major open-source
50 to Pigweed with any past experience with GN.
51 #. **No reusable rulesets.** Pigweed has written and maintains all its GN
[all …]
|