| /external/bazelbuild-rules_python/docs/ |
| D | toolchains.md | 1 :::{default-domain} bzl
6 This documents how to configure the Python toolchain and runtimes for different
16 2. A library module with dev-only uses of Python. For example, a Java project
18 3. A library module without version constraints. For example, a rule set with
19 Python build tools, but defers to the user as to what Python version is used
21 4. A library module with version constraints. For example, a rule set with
22 Python build tools, and the module requires a specific version of Python
27 Root modules are always the top-most module. These are special in two ways:
34 explicitly specify the Python version you want to use. This ensures that
35 dependencies don't change the Python version out from under you. Remember that
[all …]
|
| /external/cronet/stable/third_party/rust/chromium_crates_io/vendor/zerocopy-0.7.35/ |
| D | cargo.sh | 5 # Licensed under a BSD-style license <LICENSE-BSD>, Apache License, Version 2.0
6 # <LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0>, or the MIT
7 # license <LICENSE-MIT or https://opensource.org/licenses/MIT>, at your option.
11 # This script is a thin wrapper around Cargo that provides human-friendly
12 # toolchain names which are automatically translated to the toolchain versions
15 # cargo.sh --version <toolchain-name> # looks up the version for the named toolchain
16 # cargo.sh +<toolchain-name> [...] # runs cargo commands with the named toolchain
17 # cargo.sh +all [...] # runs cargo commands with each toolchain
19 # The meta-toolchain "all" instructs this script to run the provided command
20 # once for each toolchain (msrv, stable, nightly).
[all …]
|
| /external/rust/android-crates-io/extra_versions/crates/zerocopy/ |
| D | cargo.sh | 5 # Licensed under a BSD-style license <LICENSE-BSD>, Apache License, Version 2.0
6 # <LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0>, or the MIT
7 # license <LICENSE-MIT or https://opensource.org/licenses/MIT>, at your option.
11 # This script is a thin wrapper around Cargo that provides human-friendly
12 # toolchain names which are automatically translated to the toolchain versions
15 # cargo.sh --version <toolchain-name> # looks up the version for the named toolchain
16 # cargo.sh +<toolchain-name> [...] # runs cargo commands with the named toolchain
17 # cargo.sh +all [...] # runs cargo commands with each toolchain
19 # The meta-toolchain "all" instructs this script to run the provided command
20 # once for each toolchain (msrv, stable, nightly).
[all …]
|
| /external/cronet/tot/third_party/rust/chromium_crates_io/vendor/zerocopy-0.7.35/ |
| D | cargo.sh | 5 # Licensed under a BSD-style license <LICENSE-BSD>, Apache License, Version 2.0
6 # <LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0>, or the MIT
7 # license <LICENSE-MIT or https://opensource.org/licenses/MIT>, at your option.
11 # This script is a thin wrapper around Cargo that provides human-friendly
12 # toolchain names which are automatically translated to the toolchain versions
15 # cargo.sh --version <toolchain-name> # looks up the version for the named toolchain
16 # cargo.sh +<toolchain-name> [...] # runs cargo commands with the named toolchain
17 # cargo.sh +all [...] # runs cargo commands with each toolchain
19 # The meta-toolchain "all" instructs this script to run the provided command
20 # once for each toolchain (msrv, stable, nightly).
[all …]
|
| /external/trusty/arm-trusted-firmware/make_helpers/ |
| D | toolchain.mk | 2 # Copyright (c) 2023-2024, Arm Limited and Contributors. All rights reserved.
4 # SPDX-License-Identifier: BSD-3-Clause
8 # TF-A uses three toolchains:
10 # - The host toolchain (`host`) for building native tools
11 # - The AArch32 toolchain (`aarch32`) for building Arm AArch32 images
12 # - The AArch64 toolchain (`aarch64`) for building Arm AArch64 images
18 ifndef toolchain-mk
19 toolchain-mk := $(lastword $(MAKEFILE_LIST))
21 include $(dir $(toolchain-mk))build_env.mk
22 include $(dir $(toolchain-mk))utilities.mk
[all …]
|
| /external/bazelbuild-rules_rust/rust/ |
| D | repositories.bzl | 34 # Re-export `load_arbitrary_tool` as it's historically been used in external repositories.
39 "aarch64-apple-darwin": "rust_darwin_aarch64",
40 "aarch64-pc-windows-msvc": "rust_windows_aarch64",
41 "aarch64-unknown-linux-gnu": "rust_linux_aarch64",
42 "x86_64-apple-darwin": "rust_darwin_x86_64",
43 "x86_64-pc-windows-msvc": "rust_windows_x86_64",
44 "x86_64-unknown-freebsd": "rust_freebsd_x86_64",
45 "x86_64-unknown-linux-gnu": "rust_linux_x86_64",
55 …mirror.bazel.build/github.com/bazelbuild/platforms/releases/download/0.0.8/platforms-0.0.8.tar.gz",
56 … "https://github.com/bazelbuild/platforms/releases/download/0.0.8/platforms-0.0.8.tar.gz",
[all …]
|
| D | extensions.bzl | 30 # Toolchain configuration is only allowed in the root module, or in
35 toolchains = root.tags.toolchain or rules_rust.tags.toolchain
37 for toolchain in toolchains:
39 dev_components = toolchain.dev_components,
40 edition = toolchain.edition,
41 allocator_library = toolchain.allocator_library,
42 rustfmt_version = toolchain.rustfmt_version,
43 rust_analyzer_version = toolchain.rust_analyzer_version,
44 sha256s = toolchain.sha256s,
45 extra_target_triples = toolchain.extra_target_triples,
[all …]
|
| /external/swiftshader/tests/regres/llvm/ |
| D | llvm.go | 3 // Licensed under the Apache License, Version 2.0 (the "License");
7 // http://www.apache.org/licenses/LICENSE-2.0
37 // Version holds the build version information of an LLVM toolchain.
38 type Version struct { struct
42 func (v Version) String() string { argument
47 func (v Version) GreaterEqual(rhs Version) bool { argument
63 // Download downloads and verifies the LLVM toolchain for the current OS.
64 func (v Version) Download() ([]byte, error) { argument
68 // DownloadForOS downloads and verifies the LLVM toolchain for the given OS.
69 func (v Version) DownloadForOS(osName string) ([]byte, error) { argument
[all …]
|
| /external/bazelbuild-rules_rust/examples/bzlmod/proto/ |
| D | README.md | 5 all binary targets apply optimization from the [compiler optimization example](../03-comp-opt).
10 cargo run --bin grpc_server
16 cargo run --bin grpc_client
31 The Prost and Tonic rules do not specify a default toolchain in order to avoid mismatched dependenc…
32 While the Tonic toolchain works out of the box when its dependencies are matched, however,
33 Prost requires a custom toolchain that you have to define.
37 2. Configure a custom Prost toolchain
38 3. Register custom Prost toolchain.
50 bazel_dep(name = "rules_proto", version = "6.0.2")
51 # https://github.com/aspect-build/toolchains_protoc/releases
[all …]
|
| /external/bazelbuild-rules_rust/examples/bzlmod/proto_with_toolchain/ |
| D | README.md | 5 all binary targets apply optimization from the [compiler optimization example](../03-comp-opt).
10 cargo run --bin grpc_server
16 cargo run --bin grpc_client
31 The Prost and Tonic rules do not specify a default toolchain in order to avoid mismatched dependenc…
32 While the Tonic toolchain works out of the box when its dependencies are matched, however,
33 Prost requires a custom toolchain that you have to define.
37 2. Configure a custom Prost toolchain
38 3. Register custom Prost toolchain.
50 bazel_dep(name = "rules_proto", version = "6.0.2")
51 # https://github.com/aspect-build/toolchains_protoc/releases
[all …]
|
| /external/bazelbuild-rules_python/python/private/ |
| D | python.bzl | 3 # Licensed under the Apache License, Version 2.0 (the "License");
7 # http://www.apache.org/licenses/LICENSE-2.0
15 "Python toolchain module extensions for use with bzlmod."
44 element is special and is treated as the default toolchain.
58 # NOTE: The last element is special: it is treated as the default toolchain,
62 # We store the default toolchain separately to ensure it is the last
63 # toolchain added to toolchains.
74 # if the root module does not register any toolchain then the
76 if not module_ctx.modules[0].tags.toolchain:
101 # toolchain for a couple reasons:
[all …]
|
| D | py_toolchain_suite.bzl | 3 # Licensed under the Apache License, Version 2.0 (the "License");
7 # http://www.apache.org/licenses/LICENSE-2.0
15 """Create the toolchain defs in a BUILD.bazel file."""
28 # buildifier: disable=unnamed-macro
40 prefix: Prefix for toolchain target names.
42 python_version: The full (X.Y.Z) version of the interpreter.
44 flag_values: Extra flag values to match for this toolchain.
51 # toolchain file.
101 native.toolchain(
103 toolchain = "@{runtime_repo_name}//:python_runtimes".format(
[all …]
|
| /external/bazelbuild-rules_go/go/private/ |
| D | extensions.bzl | 8 """.format(repr(ctx.attr.toolchain)))
13 # We cannot use attr.label for the `toolchain` attribute since the module extension cannot
15 "toolchain": attr.string(
16 … apparent label of a `ROOT` file in the repository of a host compatible toolchain created by the `…
20 doc = "An external repository to expose the first host compatible toolchain",
30 "version": attr.string(),
38 "version": attr.string(),
55 # We remember the first host compatible toolchain declared by the download and host tags.
63 # SDKs without an explicit version are fetched even when not selected by toolchain
66 if not module.is_root and not download_tag.version:
[all …]
|
| /external/coreboot/ |
| D | toolchain.mk | 1 # SPDX-License-Identifier: GPL-2.0-only
22 # scan-build integration
26 export CCC_ANALYZER_ANALYSIS := -analyzer-opt-analyze-headers
36 # include-what-you-use integration
41 $(error include-what-you-use selected, but not found in PATH)
47 CFLAGS_common := -Xiwyu --prefix_header_includes=remove -Xiwyu --no_comments -Xiwyu --no_fwd_decl…
52 MAP-decompressor := bootblock
54 ARCHDIR-i386 := x86
55 ARCHDIR-x86_32 := x86
56 ARCHDIR-x86_64 := x86
[all …]
|
| /external/bazelbuild-rules_java/toolchains/ |
| D | remote_java_repository.bzl | 3 # Licensed under the Apache License, Version 2.0 (the "License");
7 # http://www.apache.org/licenses/LICENSE-2.0
17 Rule remote_java_repository imports a JDK and creates toolchain definitions for it.
35 def remote_java_repository(name, version, target_compatible_with = None, prefix = "remotejdk", **kw…
36 """Imports a JDK from a http archive and creates runtime toolchain definitions for it.
41 Toolchain resolution is determined with target_compatible_with
42 parameter and constrained with --java_runtime_version flag either having value
43 of "version" or "{prefix}_{version}" parameters.
47 version: Version of the JDK imported.
54 build_file_content = JDK_BUILD_TEMPLATE.format(RUNTIME_VERSION = version),
[all …]
|
| /external/bazelbuild-rules_rust/docs/ |
| D | rust_proto.vm | 7 `rust_grpc_library` rules which generate Rust code using the [`rust-protobuf`] dependencies.
9 [rust]: http://www.rust-lang.org/
10 [protobuf]: https://developers.google.com/protocol-buffers/
12 [`rust-protobuf`]: https://github.com/stepancheg/rust-protobuf/
28 The `prost` and `tonic` rules do not specify a default toolchain in order to avoid mismatched
29 dependency issues. To setup the `prost` and `tonic` toolchain, please see the section
30 [Customizing `prost` and `tonic` Dependencies](#custom-prost-deps).
34 #### <a name="custom-prost-deps">Customizing `prost` and `tonic` Dependencies
36 These rules depend on the [`prost`] and [`tonic`] dependencies. To setup the necessary toolchain
37 …se rules, you must define a toolchain with the [`prost`], [`prost-types`], [`tonic`], [`protoc-gen…
[all …]
|
| /external/sandboxed-api/ |
| D | MODULE.bazel.lock | 5 …"https://bcr.bazel.build/modules/abseil-cpp/20210324.2/MODULE.bazel": "7cd0312e064fde87c8d1cd79ba0…
6 …"https://bcr.bazel.build/modules/abseil-cpp/20211102.0/MODULE.bazel": "70390338f7a5106231d20620712…
7 …"https://bcr.bazel.build/modules/abseil-cpp/20230125.1/MODULE.bazel": "89047429cb0207707b2dface14b…
8 …"https://bcr.bazel.build/modules/abseil-cpp/20230802.0.bcr.1/MODULE.bazel": "1c8cec495288dccd14fda…
9 …"https://bcr.bazel.build/modules/abseil-cpp/20230802.0/MODULE.bazel": "d253ae36a8bd9ee3c5955384096…
10 …"https://bcr.bazel.build/modules/abseil-cpp/20240116.1/MODULE.bazel": "37bcdb4440fbb61df6a1c296ae0…
11 …"https://bcr.bazel.build/modules/abseil-cpp/20240116.2/MODULE.bazel": "73939767a4686cd9a520d16af5a…
12 …"https://bcr.bazel.build/modules/abseil-cpp/20240722.0/MODULE.bazel": "88668a07647adbdc14cb3a7cd11…
13 …"https://bcr.bazel.build/modules/abseil-cpp/20240722.0/source.json": "59af9f8a8a4817092624e21263fe…
14 …"https://bcr.bazel.build/modules/abseil-py/2.1.0/MODULE.bazel": "5ebe5bf853769c65707e5c28f216798f7…
[all …]
|
| /external/bazelbuild-rules_rust/examples/bzlmod/cross_compile/ |
| D | MODULE.bazel | 3 version = "0.0.0",
7 bazel_dep(name = "rules_rust", version = "0.46.0")
14 bazel_dep(name = "toolchains_musl", version = "0.1.16", dev_dependency = True)
17 bazel_dep(name = "platforms", version = "0.0.10")
19 # https://github.com/bazel-contrib/toolchains_llvm
20 bazel_dep(name = "toolchains_llvm", version = "1.0.0")
25 # Both, cross compilation and MUSL still need a C/C++ toolchain with sysroot.
35 # https://commondatastorage.googleapis.com/chrome-linux-sysroot/
40 …urls = ["https://commondatastorage.googleapis.com/chrome-linux-sysroot/toolchain/2e7ada854015a4cc6…
47 …urls = ["https://commondatastorage.googleapis.com/chrome-linux-sysroot/toolchain/41a6c8dec4c4304d6…
[all …]
|
| D | README.md | 7 * {linux, x86_64} -> {linux, aarch64}
8 * {darwin, x86_64} -> {linux, x86_64}
9 * {darwin, x86_64} -> {linux, aarch64}
10 * {darwin, aarch64 (Apple Silicon)} -> {linux, x86_64}
11 * {darwin, aarch64 (Apple Silicon)} -> {linux, aarch64}
13 You cross-compile by calling the target.
43 bazel_dep(name = "platforms", version = "0.0.10")
44 # https://github.com/bazel-contrib/toolchains_llvm
45 bazel_dep(name = "toolchains_llvm", version = "1.0.0")
50 Next, you have to configure the LLVM toolchain because rules_rust still needs a cpp toolchain for c…
[all …]
|
| /external/angle/build/docs/ |
| D | mac_hermetic_toolchain.md | 1 # Mac and iOS hermetic toolchain instructions
3 The following is a short explanation of why we use a the hermetic toolchain
4 and instructions on how to roll a new toolchain. This toolchain is only
7 ## How to roll a new hermetic toolchain.
9 1. Download a new version of Xcode, and confirm either mac or ios builds
10 properly with this new version.
16 The CIPD package creates a subset of the toolchain necessary for a build.
19 [mac_toolchain.py](../mac_toolchain.py) with the version created by the
24 ## Why we use a hermetic toolchain.
28 Chrome ships its own version of clang (compiler), but is dependent on Xcode
[all …]
|
| /external/cronet/stable/build/docs/ |
| D | mac_hermetic_toolchain.md | 1 # Mac and iOS hermetic toolchain instructions
3 The following is a short explanation of why we use a the hermetic toolchain
4 and instructions on how to roll a new toolchain. This toolchain is only
7 ## How to roll a new hermetic toolchain.
9 1. Download a new version of Xcode, and confirm either mac or ios builds
10 properly with this new version.
16 The CIPD package creates a subset of the toolchain necessary for a build.
19 [mac_toolchain.py](../mac_toolchain.py) with the version created by the
24 ## Why we use a hermetic toolchain.
28 Chrome ships its own version of clang (compiler), but is dependent on Xcode
[all …]
|
| /external/cronet/tot/build/docs/ |
| D | mac_hermetic_toolchain.md | 1 # Mac and iOS hermetic toolchain instructions
3 The following is a short explanation of why we use a the hermetic toolchain
4 and instructions on how to roll a new toolchain. This toolchain is only
7 ## How to roll a new hermetic toolchain.
9 1. Download a new version of Xcode, and confirm either mac or ios builds
10 properly with this new version.
16 The CIPD package creates a subset of the toolchain necessary for a build.
19 [mac_toolchain.py](../mac_toolchain.py) with the version created by the
24 ## Why we use a hermetic toolchain.
28 Chrome ships its own version of clang (compiler), but is dependent on Xcode
[all …]
|
| /external/bazelbuild-rules_cc/cc/ |
| D | find_cc_toolchain.bzl | 1 # pylint: disable=g-bad-file-header
4 # Licensed under the Apache License, Version 2.0 (the "License");
8 # http://www.apache.org/licenses/LICENSE-2.0
19 Rules that require a CC toolchain should call `use_cc_toolchain` and `find_cc_toolchain`
20 to depend on and find a cc toolchain.
23 C++ toolchain is selected using the legacy mechanism (`--crosstool_top`,
24 `--cpu`, `--compiler`). For that to work the rule needs to declare an
39 C++ toolchain is selected using the toolchain resolution mechanism
40 (`--platforms`). For that to work the rule needs to declare a dependency on
41 C++ toolchain type:
[all …]
|
| /external/coreboot/util/crossgcc/ |
| D | Makefile.mk | 1 ## SPDX-License-Identifier: GPL-2.0-only
7 @echo '*** Toolchain targets ***'
8 @echo ' crossgcc - Build coreboot cross-compilers for all platforms'
9 @echo ' crossgcc-clean - Remove all built coreboot cross-compilers'
10 @echo ' iasl - Build coreboot IASL compiler (built by all cross targets)'
11 @echo ' clang - Build coreboot clang compiler'
12 @echo ' nasm - Build coreboot nasm'
13 @echo ' test-toolchain - Reports if toolchain components are out of date'
14 @echo ' crossgcc-ARCH - Build cross-compiler for specific architecture'
16 @echo ' Use "make [target] CPUS=#" to build toolchain using multiple cores'
[all …]
|
| /external/bazelbuild-rules_rust/crate_universe/ |
| D | BUILD.bazel | 4 load("//crate_universe:version.bzl", "VERSION")
62 # https://docs.bazel.build/versions/main/user-manual.html#workspace_status
63 # for more information). Set stamp = -1 to indicate that it should respect
64 # the value of the --stamp comandline flag.
65 stamp = -1,
66 version = VERSION,
75 version = VERSION,
92 "@rules_rust//rust/toolchain:current_cargo_files",
93 "@rules_rust//rust/toolchain:current_rustc_files",
99 "CARGO": "$(rootpath @rules_rust//rust/toolchain:current_cargo_files)",
[all …]
|