Searched +full:build +full:- +full:docs (Results 1 – 25 of 1372) sorted by relevance
12345678910>>...55
| /external/pigweed/docs/contributing/docs/ |
| D | build.rst | 1 .. _contrib-docs-build:
4 Working with the pigweed.dev build system
7 used by ``pigweed.dev``, you'll need to interact with this Bazel-based
10 Check out :ref:`contrib-docs-build-appendix-architecture` for a top-down explanation
13 .. _contrib-docs-build-quickstart:
15 ----------
17 ----------
18 #. Build the docs:
20 .. code-block:: console
22 $ bazelisk build //docs:docs
[all …]
|
| /external/python/cpython3/Doc/ |
| D | Makefile | 10 SPHINXBUILD = PATH=$(VENVDIR)/bin:$$PATH sphinx-build
17 SPHINXERRORHANDLING = -W
20 PAPEROPT_a4 = -D latex_elements.papersize=a4paper
21 PAPEROPT_letter = -D latex_elements.papersize=letterpaper
23 ALLSPHINXOPTS = -b $(BUILDER) \
24 -d build/doctrees \
25 -j $(JOBS) \
28 . build/$(BUILDER) $(SOURCES)
33 @echo " clean to remove build files"
48 @echo " pydoc-topics to regenerate the pydoc topics file"
[all …]
|
| /external/bazelbuild-rules_go/go/ |
| D | core.rst | 4 .. _"Make variable": https://docs.bazel.build/versions/master/be/make-variables.html
5 .. _Bourne shell tokenization: https://docs.bazel.build/versions/master/be/common-definitions.html#…
6 .. _Gazelle: https://github.com/bazelbuild/bazel-gazelle
11 .. _build constraints: https://golang.org/pkg/go/build/#hdr-Build_Constraints
12 .. _cc_library deps: https://docs.bazel.build/versions/master/be/c-cpp.html#cc_library.deps
14 .. _config_setting: https://docs.bazel.build/versions/master/be/general.html#config_setting
15 .. _data dependencies: https://docs.bazel.build/versions/master/build-ref.html#data
18 .. _mode attributes: modes.rst#mode-attributes
23 .. _select: https://docs.bazel.build/versions/master/be/functions.html#select
24 .. _shard_count: https://docs.bazel.build/versions/master/be/common-definitions.html#test.shard_cou…
[all …]
|
| /external/pigweed/pw_docgen/ |
| D | docs.rst | 1 .. _module-pw_docgen:
6 .. pigweed-module::
9 ``pw_docgen`` provides tools to generate documentation for Pigweed-based
16 --------
18 --------
19 Pigweed-based projects typically use a subset of Pigweed's modules and add their
20 own product-specific modules on top of that, which may have product-specific
26 The documentation generation is integrated directly into the build system. Any
27 build target can depend on documentation, which allows it to be included as part
28 of a factory release build, for example. Additionally, documentation itself can
[all …]
|
| /external/bazelbuild-rules_python/sphinxdocs/docs/ |
| D | readthedocs.md | 1 :::{default-domain} bzl
4 # Read the Docs integration
7 to build for, and deploy to, Read the Docs. It does this by having Bazel do
8 all the work of building, and then the outputs are copied to where Read the Docs
10 you have more certainty that the docs you generate locally will match what
11 is created in the Read the Docs build environment.
13 Setting this up is conceptually simple: make the Read the Docs build call `bazel
19 In order for Read the Docs to call our custom commands, we have to use the
20 advanced `build.commands` setting of the config file. This needs to do two key
29 `--@rules_python//sphinxdocs:extra_env` and
[all …]
|
| /external/pigweed/docs/blog/ |
| D | 08-bazel-docgen.rst | 1 .. _blog-08-bazel-docgen:
6 *Published on 2025-02-03 by Kayce Basques*
10 * :ref:`blog-08-bazel-docgen-why`
11 * :ref:`blog-08-bazel-docgen-compare`
12 * :ref:`blog-08-bazel-docgen-good`
13 * :ref:`blog-08-bazel-docgen-challenges`
14 * :ref:`blog-08-bazel-docgen-next`
19 post merely discusses how we migrated the build for our own docs site
22 .. _blog-08-bazel-docgen-why:
24 ---------------------------------
[all …]
|
| /external/pytorch/.github/workflows/ |
| D | _docs.yml | 1 name: build docs
6 build-environment:
9 description: Top-level label for what's being built/tested.
10 docker-image:
18 description: If set, push the docs to the docs website.
19 run-doxygen:
24 sync-tag:
30 job with the same `sync-tag` is identical.
31 s3-bucket:
35 default: "gha-artifacts"
[all …]
|
| /external/llvm/docs/ |
| D | README.txt | 8 system to create HTML pages which are hosted on <http://llvm.org/docs/> and
12 Sphinx <http://sphinx-doc.org/> and then do:
14 cd <build-dir>
15 cmake -DLLVM_ENABLE_SPHINX=true -DSPHINX_OUTPUT_HTML=true <src-dir>
16 make -j3 docs-llvm-html
17 $BROWSER <build-dir>/docs//html/index.html
20 `docs/Foo.rst` <-> `<build-dir>/docs//html/Foo.html` <-> `http://llvm.org/docs/Foo.html`.
33 directory `<build-dir>/docs/man/`.
35 cd <build-dir>
36 cmake -DLLVM_ENABLE_SPHINX=true -DSPHINX_OUTPUT_MAN=true <src-dir>
[all …]
|
| /external/python/parse_type/tasks/ |
| D | docs.py | 1 # -*- coding: UTF-8 -*-
3 Provides tasks to build documentation with sphinx, etc.
13 # -- TASK-LIBRARY:
17 # -----------------------------------------------------------------------------
19 # -----------------------------------------------------------------------------
23 # -----------------------------------------------------------------------------
25 # -----------------------------------------------------------------------------
33 # -- CASE: not LANGUAGE-SPECIFIC
34 destdir = Path(ctx.config.sphinx.destdir or "build")/builder
36 # -- CASE: LANGUAGE-SPECIFIC:
[all …]
|
| /external/bazel-skylib/ |
| D | README.md | 3 [) and access the symbols by
45 * [collections](docs/collections_doc.md)
46 * [dicts](docs/dicts_doc.md)
47 * [partial](docs/partial_doc.md)
[all …]
|
| /external/pytorch/ |
| D | .gitignore | 5 # if you delete aten/build/ because it's redundant with build/,
6 # aten/build/ will stop being cleaned. So be careful when
20 **/.pytorch-disabled-tests.json
31 aten/build/
37 docs/build/
38 docs/cpp/src
39 docs/src/**/*
40 docs/cpp/build
41 docs/cpp/source/api
42 docs/cpp/source/html/
[all …]
|
| D | .dockerignore | 5 # if you delete aten/build/ because it's redundant with build/,
6 # aten/build/ will stop being cleaned. So be careful when
20 **/.pytorch-disabled-tests.json
31 aten/build/
37 docs/build/
38 docs/cpp/src
39 docs/src/**/*
40 docs/cpp/build
41 docs/cpp/source/api
42 docs/cpp/source/html/
[all …]
|
| /external/skia/site/docs/dev/contrib/ |
| D | bazel.md | 2 ---
6 ---
10 Skia is currently migrating towards using [Bazel](https://bazel.build/) as a build system, due to
14 [Bazel label notation](https://bazel.build/concepts/labels), so to refer the file located at
15 `$SKIA_ROOT/docs/examples/Arc.cpp`, we would say `//docs/examples/Arc.cpp`.
18 The Bazel docs are quite good. Suggested reading order if you are new to Bazel:
19 - [Getting Started with Bazel and C++](https://bazel.build/tutorials/cpp)
20 - [WORKSPACE.bazel and external deps](https://bazel.build/docs/external)
21 - [Targets and Labels](https://bazel.build/concepts/labels)
22 - [Understanding a build](https://bazel.build/docs/build)
[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_python/docs/ |
| D | README.md | 1 # rules_python Sphinx docs generation
3 The docs for rules_python are generated using a combination of Sphinx, Bazel,
6 MyST-specific Markdown functionality.
11 Manually building the docs isn't necessary -- readthedocs.org will
12 automatically build and deploy them when commits are pushed to the repo.
14 ## Generating docs for development
16 Generating docs for development is a two-part process: starting a local HTTP
17 server to serve the generated HTML, and re-generating the HTML when sources
21 bazel run //docs:docs.serve # Run in separate terminal
22 ibazel build //docs:docs # Automatically rebuilds docs
[all …]
|
| /external/pigweed/docs/ |
| D | style_guide.rst | 1 .. _docs-pw-style:
11 ``pw presubmit --install``
15 .. grid-item-card:: :octicon:`diff-added` C++ style
16 :link: docs-pw-style-cpp
17 :link-type: ref
18 :class-item: sales-pitch-cta-primary
24 .. grid-item-card:: :octicon:`pencil` Commit messages
25 :link: docs-pw-style-commit-message
26 :link-type: ref
27 :class-item: sales-pitch-cta-secondary
[all …]
|
| /external/webrtc/docs/native-code/development/prerequisite-sw/ |
| D | index.md | 1 # WebRTC development - Prerequisite software
5 1. [Install the Chromium depot tools][depot-tools].
17 $ ./build/install-build-deps.sh
21 build using Debian sysroot images in build/linux, but there are still some tools
22 needed for the build that are installed with
23 [install-build-deps.sh][install-build-deps].
25 You may also want to have a look at the [Chromium Linux Build
26 instructions][chromium-linux-build-instructions] if you experience any other problems building.
30 Follow the [Chromium's build instructions for Windows][chromium-win-build-instructions].
39 Xcode 12 or higher is required. Latest Xcode is recommended to be able to build
[all …]
|
| /external/pigweed/docs/get_started/ |
| D | upstream.rst | 1 .. _docs-get-started-upstream:
9 :ref:`docs-get-started` if you're looking for instructions on how to use
22 If you haven't already, :ref:`docs-first-time-setup`.
24 -------------
26 -------------
29 all the steps to :ref:`docs-first-time-setup`. The express setup
32 #. **Host** - Mac, Linux, or Windows. Builds and runs tests
33 #. **Device/STM32F429** - Build only; Optionally, the STM32F429I-DISC1 kit to
35 #. **Docs** - Builds the Pigweed docs
44 .. code-block:: bash
[all …]
|
| /external/aws-sdk-java-v2/services-custom/iam-policy-builder/src/main/java/software/amazon/awssdk/policybuilder/iam/ |
| D | IamStatement.java | 48 * <li>A is the <b>principal</b> - the AWS account that is making a request to
50 …* <li>B is the <b>action</b> - the way in which your AWS resource is being accessed or modified,…
52 * <li>C is the <b>resource</b> - your AWS entity that the principal wants to access, such
54 * <li>D is the set of <b>conditions</b> - optional constraints that specify when to allow or deny
68 …* For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/">The IAM Us…
72 …* <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_id-based…
80 * .addResource("arn:aws:dynamodb:us-east-2:123456789012:table/books")
81 * .build();
86 …* <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_resource…
93 * .build();
[all …]
|
| /external/pigweed/pw_build/py/ |
| D | project_builder_prefs_test.py | 7 # https://www.apache.org/licenses/LICENSE-2.0
39 def _create_tempfile(content: str) -> Path:
43 output_file.write(content.encode('UTF-8'))
52 def test_load_no_existing_files(self) -> None:
69 prefs._config, expected_config # pylint: disable=protected-access
75 'Manual --build-system-commands on the command line',
78 '--build-system-command',
80 'bazel build',
81 '--build-system-command',
94 'extra_args': ['build'],
[all …]
|
| /external/google-benchmark/ |
| D | README.md | 3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …st-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://githu…
33 [User Guide](docs/user_guide.md) for a more comprehensive feature overview.
35 …read the [Google Test documentation](https://github.com/google/googletest/blob/main/docs/primer.md)
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
45 [Additional Tooling Documentation](docs/tools.md)
47 [Assembly Testing Documentation](docs/AssemblyTests.md)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++14 to build,
56 _See [dependencies.md](docs/dependencies.md) for more details regarding supported
[all …]
|
| /external/cronet/tot/third_party/google_benchmark/src/ |
| D | README.md | 3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …st-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://githu…
33 [User Guide](docs/user_guide.md) for a more comprehensive feature overview.
35 …read the [Google Test documentation](https://github.com/google/googletest/blob/main/docs/primer.md)
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
45 [Additional Tooling Documentation](docs/tools.md)
47 [Assembly Testing Documentation](docs/AssemblyTests.md)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++14 to build,
56 _See [dependencies.md](docs/dependencies.md) for more details regarding supported
[all …]
|
| /external/cronet/stable/third_party/google_benchmark/src/ |
| D | README.md | 3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …st-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://githu…
33 [User Guide](docs/user_guide.md) for a more comprehensive feature overview.
35 …read the [Google Test documentation](https://github.com/google/googletest/blob/main/docs/primer.md)
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
45 [Additional Tooling Documentation](docs/tools.md)
47 [Assembly Testing Documentation](docs/AssemblyTests.md)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++14 to build,
56 _See [dependencies.md](docs/dependencies.md) for more details regarding supported
[all …]
|
| /external/google-cloud-java/java-dlp/google-cloud-dlp/src/main/java/com/google/cloud/dlp/v2/ |
| D | DlpServiceClient.java | 8 * https://www.apache.org/licenses/LICENSE-2.0
99 // AUTO-GENERATED DOCUMENTATION AND CLASS.
102 * detect the presence of Personally Identifiable Information (PII) and other privacy-sensitive data
103 * in user-supplied, unstructured data streams, like text blocks or images. The service also
107 * <p>To learn more about concepts and find how-to guides see https://cloud.google.com/dlp/docs/.
115 * // - It may require correct/in-range values for request initialization.
116 * // - It may require specifying regional endpoints when creating the service client as shown in
117 * // https://cloud.google.com/java/docs/setup#configure_endpoints_for_the_client_library
122 * .setInspectConfig(InspectConfig.newBuilder().build())
123 * .setItem(ContentItem.newBuilder().build())
[all …]
|
| /external/angle/build/ |
| D | README.md | 2 `//build` contains:
4 * Core Python build scripts
7 v8, etc), it should be kept as self-contained as possible by not referring
12 Changes to `//build` should be landed in the Chromium repo. They will then be
13 replicated to the stand-alone [build repo](https://chromium.googlesource.com/chromium/src/build)
19 * `//build/config` - Common templates via `.gni` files.
20 * `//build/toolchain` - GN toolchain definitions.
21 * `Other .py files` - Some are used by GN/Ninja. Some by gclient hooks, some
25 * `//build/BUILDCONFIG.gn` - Included by all `BUILD.gn` files.
26 * `//build/secondary` - An overlay for `BUILD.gn` files. Enables adding
[all …]
|
12345678910>>...55