| /external/bazelbuild-rules_testing/docs/ |
| D | crossrefs.md | 1 [`Action`]: https://bazel.build/rules/lib/Action
3 [`bool`]: https://bazel.build/rules/lib/bool
6 [`depset`]: https://bazel.build/rules/lib/depset
8 [`dict`]: https://bazel.build/rules/lib/dict
12 [`File`]: https://bazel.build/rules/lib/File
14 [`format_str`]: /api/expect_meta.html#expectmeta-format-str
16 [`Label`]: https://bazel.build/rules/lib/Label
18 [`list`]: https://bazel.build/rules/lib/list
21 [`str`]: https://bazel.build/rules/lib/string
22 [`struct`]: https://bazel.build/rules/lib/builtins/struct
[all …]
|
| /external/mesa3d/.gitlab-ci/container/ |
| D | gitlab-ci.yml | 3 .incorporate-templates-commit:
5 FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_TEMPLATES_COMMIT}"
7 .incorporate-base-tag+templates-commit:
9 …FDO_BASE_IMAGE: "${CI_REGISTRY_IMAGE}/${MESA_BASE_IMAGE}:${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT…
10 FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT}"
12 .set-image:
14 - .incorporate-templates-commit
19 .set-image-base-tag:
21 - .set-image
22 - .incorporate-base-tag+templates-commit
[all …]
|
| /external/mesa3d/.gitlab-ci/ |
| D | test-source-dep.yml | 5 .scheduled_pipeline-rules:
6 rules:
7 - if: &is-scheduled-pipeline '$CI_PIPELINE_SOURCE == "schedule"'
14 - api_failure
15 - runner_system_failure
16 - scheduler_failure
17 - data_integrity_failure
18 - unknown_failure
23 .no_scheduled_pipelines-rules:
24 rules:
[all …]
|
| /external/stardoc/docs/ |
| D | generating_stardoc.md | 4 <li><a href="#single-file">Single File</a></li>
5 <li><a href="#files-with-deps">Files with Dependencies</a></li>
6 <li><a href="#multiple-files">Multiple Files</a></li>
12 <a name="single-file"></a>
15 Suppose you have a project containing Stardoc rules you want to document:
21 BUILD
25 To generate documentation for the rules in `checkstyle.bzl`, add the
26 following target to `rules/BUILD`:
32 name = "checkstyle-docs",
38 Running `bazel build //checkstyle:checkstyle-docs` will generate a markdown file
[all …]
|
| /external/bazelbuild-rules_go/docs/go/core/ |
| D | rules.bzl | 2 ["Make variable"]: https://docs.bazel.build/versions/master/be/make-variables.html
3 …[Bourne shell tokenization]: https://docs.bazel.build/versions/master/be/common-definitions.html#s…
4 [Gazelle]: https://github.com/bazelbuild/bazel-gazelle
9 [build constraints]: https://golang.org/pkg/go/build/#hdr-Build_Constraints
10 [cc_library deps]: https://docs.bazel.build/versions/master/be/c-cpp.html#cc_library.deps
12 [config_setting]: https://docs.bazel.build/versions/master/be/general.html#config_setting
13 [data dependencies]: https://docs.bazel.build/versions/master/build-ref.html#data
16 [mode attributes]: /go/modes.rst#mode-attributes
21 [select]: https://docs.bazel.build/versions/master/be/functions.html#select
22 …[shard_count]: https://docs.bazel.build/versions/master/be/common-definitions.html#test.shard_count
[all …]
|
| /external/bazelbuild-rules_rust/docs/ |
| D | index.md | 1 # [Rules rust](https://github.com/bazelbuild/rules_rust)
5 This repository provides rules for building [Rust][rust] projects with [Bazel][bazel].
7 [bazel]: https://bazel.build/
8 [rust]: http://www.rust-lang.org/
10 <!-- TODO: Render generated docs on the github pages site again, https://bazelbuild.github.io/rules…
16 To use the Rust rules, add the following to your `WORKSPACE` file to add the external repositories …
26 …urls = ["https://github.com/bazelbuild/rules_rust/releases/download/0.31.0/rules_rust-v0.31.0.tar.…
36 The rules are released, and releases can be found on [the GitHub Releases page](https://github.com/…
38 ## Rules section in [Rules rust](https://github.com/bazelbuild/rules_rust)
40 - [defs](defs.md): standard rust rules for building and testing libraries and binaries.
[all …]
|
| /external/bazelbuild-rules_python/ |
| D | README.md | 1 # Python Rules for Bazel
3 …Build status](https://badge.buildkite.com/1bcfe58b6f5741aacb09b12485969ba7a1205955a45b53e854.svg?b…
7 This repository is the home of the core Python rules -- `py_library`,
9 support in Bazel. It also contains package installation rules for integrating with PyPI and other i…
14 [Bazel Build Encyclopedia](https://docs.bazel.build/versions/master/be/python.html).
18 Currently, the core rules build into the Bazel binary, and the symbols in this
19 …rules to Starlark and removing them from the Bazel binary. Therefore, the future-proof way to depe…
21 The core rules are stable. Their implementation in Bazel is subject to Bazel's
22 [backward compatibility policy](https://docs.bazel.build/versions/master/backward-compatibility.htm…
30 - Status: Beta
[all …]
|
| /external/pigweed/pw_toolchain_bazel/ |
| D | api.rst | 1 .. _module-pw_toolchain_bazel-api:
6 .. pigweed-module-subpage::
15 …* Which `well-known features <https://bazel.build/docs/cc-toolchain-config-reference#wellknown-fea…
32 :py:class:`pw_cc_flag_set` rules.
44 …See `cc_common.create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_commo…
49 …See `cc_common.create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_commo…
54 …See `cc_common.create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_commo…
59 …See `cc_common.create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_commo…
64 …See `cc_common.create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_commo…
69 …See `cc_common.create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_commo…
[all …]
|
| /external/libdrm/ |
| D | .gitlab-ci.yml | 1 # This is the tag of the docker image used for the build jobs. If the
8 # versions of gcc/clang or other packages, which might break the build
18 - project: 'freedesktop/ci-templates'
21 - '/templates/debian.yml'
22 - '/templates/freebsd.yml'
23 - '/templates/ci-fairy.yml'
30 - "Base container"
31 - "Build"
33 .ci-rules:
34 rules:
[all …]
|
| /external/wayland/ |
| D | .gitlab-ci.yml | 1 # This file uses the freedesktop ci-templates to build Wayland and run our
4 # ci-templates uses a multi-stage build process. First, the base container
6 # all our build dependencies. This container is aggressively cached; if a
9 # reused for the build. This gives us predictability of build and far
12 # the current date as well as a unique build identifier.
15 # previously used), the build stage executes within this container.
21 # Apart from the 'variables', 'include', and 'stages' top-level anchors,
23 # be executed as part of CI, unless the rules specify that it should not be
28 # by the ci-templates.
36 # For more information on ci-templates, see:
[all …]
|
| /external/bazelbuild-rules_cc/ |
| D | README.md | 1 # C++ rules for Bazel
3 … [.
15 There is no need to use rules from this repository just yet. If you want to use
28 Then, in your `BUILD` files, import and use the rules:
40 This repo contains an auto-detecting toolchain that expects to find tools installed on your host ma…
[all …]
|
| /external/bazelbuild-rules_android/ |
| D | README.md | 5 …w of the Starlark implementation of Android rules for Bazel. This code is incomplete and may not f…
7 … Bazel built at or near head or a recent pre-release and the following flags are necessary to use …
10 --experimental_enable_android_migration_apis
11 --experimental_google_legacy_api
12 --incompatible_java_common_parameters
13 --android_databinding_use_v3_4_args
14 --experimental_android_databinding_v2
19 This repository contains the Starlark implementation of Android rules in Bazel.
21 The rules are being incrementally converted from their native implementations
23 tree](https://source.bazel.build/bazel/+/master:src/main/java/com/google/devtools/build/lib/rules/a…
[all …]
|
| /external/pigweed/seed/ |
| D | 0113-bazel-cc-toolchain-api.rst | 1 .. _seed-0113:
10 :proposal_date: 2023-09-28
15 -------
17 -------
18 This SEED proposes custom Starlark rules for declaring C/C++ toolchains in
22 ----------
24 ----------
30 - **Underdocumented patterns**: The
31 …`create_cc_toolchain_config_info() <https://bazel.build/rules/lib/toplevel/cc_common#create_cc_too…
39 - **Not inherently modular**: Bazel expects the overwhelming majority of a
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/tools/codegen/core/ |
| D | gen_upb_api_from_bazel_xml.py | 9 # http://www.apache.org/licenses/LICENSE-2.0
18 # in Bazel BUILD file. These generate upb files are for non-Bazel build such
19 # as makefile and python build which cannot generate them at the build time.
28 # this will generate these upb source files at src/core/ext/upb-generated.
40 # Rule object representing the UPB rule of Bazel BUILD.
60 # extract actual name for alias rules
72 def get_transitive_protos(rules, t): argument
80 rule = rules.get(name, None)
93 '''Runs bazel query on given package file and returns all upb rules.'''
94 # Use a wrapper version of bazel in gRPC not to use system-wide bazel
[all …]
|
| /external/bazelbuild-rules_go/ |
| D | README.rst | 1 Go rules for Bazel_
5 .. _//tests/core/cross: https://github.com/bazelbuild/rules_go/blob/master/tests/core/cross/BUILD.b…
6 .. _Avoiding conflicts: proto/core.rst#avoiding-conflicts
7 .. _Bazel labels: https://docs.bazel.build/versions/master/build-ref.html#labels
8 .. _Bazel: https://bazel.build/
10 .. _Bzlmod: https://bazel.build/external/overview#bzlmod
12 .. _Core rules: docs/go/core/rules.md
15 .. _Deprecation schedule: https://github.com/bazelbuild/rules_go/wiki/Deprecation-schedule
17 .. _gopls integration: https://github.com/bazelbuild/rules_go/wiki/Editor-setup
18 .. _Overriding dependencies: go/dependencies.rst#overriding-dependencies
[all …]
|
| /external/tpm2-tss/ |
| D | INSTALL.md | 1 This file contains instructions to build and install the TSS libraries.
4 To build and install the tpm2-tss software the following software packages
15 * pkg-config
22 however libgcrypt-dev is required as a dependency for the configure script
24 See https://github.com/tpm2-software/tpm2-tss/issues/1365 for more info.
27 * Integration test suite (see ./configure option --enable-integration):
28 - uthash development libraries and header files
29 - ps executable (usually in the procps package)
30 - ss executable (usually in the iproute2 package)
31 - tpm_server executable (from https://sourceforge.net/projects/ibmswtpm2/)
[all …]
|
| /external/bazel-skylib/docs/ |
| D | bzl_library.md | 1 <!-- Generated with Stardoc: http://skydoc.bazel.build -->
3 Skylib module containing a library rule for aggregating rules files.
10 bzl_library(<a href="#bzl_library-name">name</a>, <a href="#bzl_library-deps">deps</a>, <a href="#b…
21 BUILD
23 BUILD
26 BUILD
31 In this case, you can have `bzl_library` targets in `checkstyle/BUILD` and
32 `lua/BUILD`:
34 `checkstyle/BUILD`:
40 name = "checkstyle-rules",
[all …]
|
| /external/grpc-grpc/tools/codegen/core/ |
| D | gen_upb_api_from_bazel_xml.py | 9 # http://www.apache.org/licenses/LICENSE-2.0
18 # in Bazel BUILD file. These generate upb files are for non-Bazel build such
19 # as makefile and python build which cannot generate them at the build time.
28 # this will generate these upb source files at src/core/ext/upb-gen.
42 # Rule object representing the UPB rule of Bazel BUILD.
62 # extract actual name for alias rules
74 def get_transitive_protos(rules, t): argument
82 rule = rules.get(name, None)
95 """Runs bazel query on given package file and returns all upb rules."""
96 # Use a wrapper version of bazel in gRPC not to use system-wide bazel
[all …]
|
| /external/oss-fuzz/docs/getting-started/new-project-guide/ |
| D | bazel.md | 1 ---
7 permalink: /getting-started/new-project-guide/bazel/
8 ---
13 - TOC
15 ---
19 The process of integrating a project using the [Bazel](https://bazel.build/)
20 build system with OSS-Fuzz is very similar to the general
21 [Setting up a new project]({{ site.baseurl }}/getting-started/new-project-guide/)
26 For Bazel-based projects, we recommend using the
30 [multiple sanitizer and fuzzing engine configurations][rules-fuzzing-usage].
[all …]
|
| /external/private-join-and-compute/third_party/abseil-cpp-20230125.2/absl/ |
| D | abseil.podspec.gen.py | 2 # -*- coding: utf-8 -*-
3 """This script generates abseil.podspec from all BUILD.bazel files.
6 It recursively analyzes BUILD.bazel files using query command of Bazel to
7 dump its build rules in XML format. From these rules, it constructs podspec
28 s.authors = { 'Abseil Team' => 'abseil-io@googlegroups.com' }
30 :git => 'https://github.com/abseil/abseil-cpp.git',
37 s.compiler_flags = '-Wno-everything'
49 # Rule object representing the rule of Bazel BUILD.
71 # e.g. ["//absl/strings:dir/header.h"] -> ["absl/strings/dir/header.h"]
90 """Runs bazel query on given package file and returns all cc rules."""
[all …]
|
| /external/cronet/third_party/abseil-cpp/absl/ |
| D | abseil.podspec.gen.py | 2 # -*- coding: utf-8 -*-
3 """This script generates abseil.podspec from all BUILD.bazel files.
6 It recursively analyzes BUILD.bazel files using query command of Bazel to
7 dump its build rules in XML format. From these rules, it constructs podspec
28 s.authors = { 'Abseil Team' => 'abseil-io@googlegroups.com' }
30 :git => 'https://github.com/abseil/abseil-cpp.git',
37 s.compiler_flags = '-Wno-everything'
49 # Rule object representing the rule of Bazel BUILD.
71 # e.g. ["//absl/strings:dir/header.h"] -> ["absl/strings/dir/header.h"]
90 """Runs bazel query on given package file and returns all cc rules."""
[all …]
|
| /external/openscreen/third_party/abseil/src/absl/ |
| D | abseil.podspec.gen.py | 2 # -*- coding: utf-8 -*-
3 """This script generates abseil.podspec from all BUILD.bazel files.
6 It recursively analyzes BUILD.bazel files using query command of Bazel to
7 dump its build rules in XML format. From these rules, it constructs podspec
28 s.authors = { 'Abseil Team' => 'abseil-io@googlegroups.com' }
30 :git => 'https://github.com/abseil/abseil-cpp.git',
37 s.compiler_flags = '-Wno-everything'
49 # Rule object representing the rule of Bazel BUILD.
71 # e.g. ["//absl/strings:dir/header.h"] -> ["absl/strings/dir/header.h"]
90 """Runs bazel query on given package file and returns all cc rules."""
[all …]
|
| /external/libtextclassifier/abseil-cpp/absl/ |
| D | abseil.podspec.gen.py | 2 # -*- coding: utf-8 -*-
3 """This script generates abseil.podspec from all BUILD.bazel files.
6 It recursively analyzes BUILD.bazel files using query command of Bazel to
7 dump its build rules in XML format. From these rules, it constructs podspec
28 s.authors = { 'Abseil Team' => 'abseil-io@googlegroups.com' }
30 :git => 'https://github.com/abseil/abseil-cpp.git',
37 s.compiler_flags = '-Wno-everything'
49 # Rule object representing the rule of Bazel BUILD.
71 # e.g. ["//absl/strings:dir/header.h"] -> ["absl/strings/dir/header.h"]
90 """Runs bazel query on given package file and returns all cc rules."""
[all …]
|
| /external/webrtc/third_party/abseil-cpp/absl/ |
| D | abseil.podspec.gen.py | 2 # -*- coding: utf-8 -*-
3 """This script generates abseil.podspec from all BUILD.bazel files.
6 It recursively analyzes BUILD.bazel files using query command of Bazel to
7 dump its build rules in XML format. From these rules, it constructs podspec
28 s.authors = { 'Abseil Team' => 'abseil-io@googlegroups.com' }
30 :git => 'https://github.com/abseil/abseil-cpp.git',
37 s.compiler_flags = '-Wno-everything'
49 # Rule object representing the rule of Bazel BUILD.
71 # e.g. ["//absl/strings:dir/header.h"] -> ["absl/strings/dir/header.h"]
90 """Runs bazel query on given package file and returns all cc rules."""
[all …]
|
| /external/angle/third_party/abseil-cpp/absl/ |
| D | abseil.podspec.gen.py | 2 # -*- coding: utf-8 -*-
3 """This script generates abseil.podspec from all BUILD.bazel files.
6 It recursively analyzes BUILD.bazel files using query command of Bazel to
7 dump its build rules in XML format. From these rules, it constructs podspec
28 s.authors = { 'Abseil Team' => 'abseil-io@googlegroups.com' }
30 :git => 'https://github.com/abseil/abseil-cpp.git',
40 s.compiler_flags = '-Wno-everything'
57 # Rule object representing the rule of Bazel BUILD.
79 # e.g. ["//absl/strings:dir/header.h"] -> ["absl/strings/dir/header.h"]
98 """Runs bazel query on given package file and returns all cc rules."""
[all …]
|