| /external/sdv/vsomeip/third_party/boost/config/.github/workflows/ |
| D | ci.yml | 10 ubuntu-focal:
11 runs-on: ubuntu-20.04
13 fail-fast: false
15 compiler: [ g++-9, g++-10, clang++-9, clang++-10 ]
17 - uses: actions/checkout@v2
19 fetch-depth: '0'
20 - uses: mstachniuk/ci-skip@v1
22 …commit-filter: '[skip ci];[ci skip];[CI SKIP];[SKIP CI];***CI SKIP***;***SKIP CI***;[windows];[Win…
23 commit-filter-separator: ';'
24 fail-fast: true
[all …]
|
| /external/toybox/mkroot/ |
| D | README | 1 mkroot - simple linux system builder
3 Compiles a toybox-based root filesystem and kernel that can boot under qemu.
6 launched via ./run-qemu.sh (which assumes you have QEMU installed, KVM
12 --- Quick Start
14 To install the build prerequisites: download toybox source, linux kernel source,
15 and one or more musl cross compiler toolchain(s) in the "ccc" directory:
19 $ wget https://landley.net/bin/toolchains/latest/i686-linux-musl-cross.tar.xz
21 $ tar xvJCf ccc i686-linux-musl-cross.tar.xz
26 $ root/i686/run-qemu.sh
31 --- Building without a cross compiler (warning: glibc sucks)
[all …]
|
| /external/autotest/site_utils/admin/ |
| D | clean_staged_images.py | 3 # Use of this source code is governed by a BSD-style license that can be
11 1. Check if the build target is in the list of targets that need to keep the
12 latest build. Skip processing the directory if that's True.
34 def get_all_timestamp_dirs(root): argument
37 @param root: The top folder to look for timestamp file.
40 for dir_path, dir_names, file_names in os.walk(root):
50 """Test to see if the build at |build_path| is older than |max_age_hours|.
52 @param build_path: The path to the build (ie. 'build_dir/R21-2035.0.0')
53 @param max_age_hours: The maximum allowed age of a build in hours.
54 @return: True if the build is older than |max_age_hours|, False otherwise.
[all …]
|
| /external/sdv/vsomeip/third_party/boost/regex/.github/workflows/ |
| D | ci.yml | 9 ubuntu-focal:
10 runs-on: ubuntu-20.04
12 fail-fast: false
14 compiler: [ g++-9, g++-10, clang++-9, clang++-10 ]
17 - uses: actions/checkout@v2
19 fetch-depth: '0'
20 - uses: mstachniuk/ci-skip@v1
22 …commit-filter: '[skip ci];[ci skip];[CI SKIP];[SKIP CI];***CI SKIP***;***SKIP CI***;[windows];[Win…
23 commit-filter-separator: ';'
24 fail-fast: true
[all …]
|
| /external/libbpf/docs/ |
| D | libbpf_build.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
8 pkg-config is used by default to find libelf, and the program called
11 If using pkg-config at build time is not desired, it can be disabled by
14 To build both static libbpf.a and shared libbpf.so:
16 .. code-block:: bash
21 To build only static libbpf.a library in directory build/ and install them
22 together with libbpf headers in a staging directory root/:
24 .. code-block:: bash
27 $ mkdir build root
28 $ BUILD_STATIC_ONLY=y OBJDIR=build DESTDIR=root make install
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/guide/ |
| D | build_ios.md | 1 # Build TensorFlow Lite for iOS
3 This document describes how to build TensorFlow Lite iOS library on your own.
4 Normally, you do not need to locally build TensorFlow Lite iOS library. If you
11 In some cases, you might wish to use a local build of TensorFlow Lite, for
15 you need to build it using Bazel on a macOS machine.
20 using `xcode-select`:
23 xcode-select --install
30 sudo xcodebuild -license accept
35 Bazel is the primary build system for TensorFlow. Install Bazel as per the
36 [instructions on the Bazel website][bazel-install]. Make sure to choose a
[all …]
|
| /external/llvm/docs/ |
| D | Projects.rst | 11 The LLVM build system is designed to facilitate the building of third party
16 to set to use the LLVM build system:
18 * ``PROJECT_NAME`` - The name by which your project is known.
19 * ``LLVM_SRC_ROOT`` - The root of the LLVM source tree.
20 * ``LLVM_OBJ_ROOT`` - The root of the LLVM object tree.
21 * ``PROJ_SRC_ROOT`` - The root of the project's source tree.
22 * ``PROJ_OBJ_ROOT`` - The root of the project's object tree.
23 * ``PROJ_INSTALL_ROOT`` - The root installation directory.
24 * ``LEVEL`` - The relative path from the current directory to the
25 project's root ``($PROJ_OBJ_ROOT)``.
[all …]
|
| D | CMake.rst | 11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
12 does not build the project, it generates the files needed by your build tool
19 If you are really anxious about getting a functional LLVM build, go to the
22 `Options and variables`_ section is a reference for customizing your build. If
25 This page is geared towards users of the LLVM CMake build. If you're looking for
26 information about modifying the LLVM CMake build system you may want to see the
34 We use here the command-line, non-interactive CMake interface.
42 #. Create a build directory. Building LLVM in the source
43 directory is not supported. cd to this directory:
45 .. code-block:: console
[all …]
|
| /external/libcxx/utils/ci/ |
| D | macos-trunk.sh | 3 set -ue
7 $(basename ${0}) [-h|--help] --libcxx-root <LIBCXX-ROOT> --libcxxabi-root <LIBCXXABI-ROOT> --std <S…
11 --libcxx-root Full path to the root of the libc++ repository to test.
12 --libcxxabi-root Full path to the root of the libc++abi repository to test.
13 --std Version of the C++ Standard to run the tests under (c++03, c++11, etc..).
14 --arch Architecture to build the tests for (32, 64).
15 …[--lit-args] Additional arguments to pass to lit (optional). If there are multiple arguments,…
16 …[--no-cleanup] Do not cleanup the temporary directory that was used for testing at the end. Thi…
17 [-h, --help] Print this help.
21 while [[ $# -gt 0 ]]; do
[all …]
|
| /external/libpcap/ |
| D | INSTALL.md | 3 with CMake and any build system supported by CMake.
5 To build libpcap with the configure script and `make`:
10 control the configuration of libpcap; `./configure --help`` will show
14 `su` to root and run `make install`. However, you need not install
15 libpcap if you just want to build tcpdump; just make sure the tcpdump
16 and libpcap directory trees have the same parent directory.
18 To build libpcap with CMake and the build system of your choice, from
21 * Create a build directory into which CMake will put the build files it
23 code directory as does the configure script. The build directory may be
24 created as a subdirectory of the source directory or as a directory
[all …]
|
| /external/libfuse/ |
| D | README.md | 5 -----
17 send responses back. libfuse offers two APIs: a "high-level",
18 synchronous API, and a "low-level" asynchronous API. In both cases,
20 callbacks. When using the high-level API, the callbacks may work with
22 finishes when the callback function returns. When using the low-level
28 ------------------
35 beyond addressing high-impact issues. When reporting bugs, please
42 -------------------
45 * BSD (mostly/best-effort)
46 * For OS-X, please use [OSXFUSE](https://osxfuse.github.io/)
[all …]
|
| /external/toybox/scripts/ |
| D | help.txt | 1 toybox - Build toybox.
2 COMMANDNAME - Build individual toybox command as a standalone binary.
3 list - List COMMANDNAMEs you can build standalone.
4 list_example - List example commands (often used by the test suite)
5 list_pending - List unfinished COMMANDNAMEs out of toys/pending.
6 change - Build each command standalone under change/.
7 baseline - Create toybox_old for use by bloatcheck.
8 bloatcheck - Report size differences between old and current versions
9 test_COMMAND - Run tests for COMMAND (test_ps, test_cat, etc.)
10 tests - Run test suite against all compiled commands.
[all …]
|
| /external/pigweed/pw_docgen/py/pw_docgen/ |
| D | docgen.py | 7 # https://www.apache.org/licenses/LICENSE-2.0
17 # to run Sphinx and build RTD docs.
39 def parse_args() -> argparse.Namespace:
40 """Parses command-line arguments."""
44 '--sphinx-build-dir',
46 help='Directory in which to build docs',
49 '--conf', required=True, help='Path to conf.py file for Sphinx'
52 '-j',
53 '--parallel',
59 '--gn-root', required=True, help='Root of the GN build tree'
[all …]
|
| /external/openscreen/tools/ |
| D | licenses.py | 3 # Use of this source code is governed by a BSD-style license that can be
36 # Paths from the root of the tree to directories to skip.
39 os.path.join('third_party', 'llvm-build'),
83 """We raise this exception when a directory's licensing info isn't
88 def AbsolutePath(path, filename, root): argument
90 root."""
92 # Absolute-looking paths are relative to the source root
93 # (which is the directory we're run from).
94 absolute_path = os.path.join(root, filename[1:])
96 absolute_path = os.path.join(root, path, filename)
[all …]
|
| /external/libchrome/build/ |
| D | landmines.py | 3 # Use of this source code is governed by a BSD-style license that can be
7 This script runs every build as the first hook (See DEPS). If it detects that
8 the build should be clobbered, it will delete the contents of the build
9 directory.
12 diff between the new landmines and the old ones is non-null. At this point, the
13 build is clobbered.
16 Doing so will wipe out every output directory on every Chrome developer's
17 machine. This can be particularly problematic on Windows where the directory
18 deletion may well fail (locked files, command prompt in the directory, etc.),
21 This output directory deletion will be repated when going back and forth across
[all …]
|
| /external/python/cpython3/Tools/msi/ |
| D | README.txt | 1 Quick Build Info
4 For testing, the installer should be built with the Tools/msi/build.bat
7 build.bat [-x86] [-x64] [-ARM64] [--doc]
13 set SPHINXBUILD=<path to sphinx-build.exe>
16 buildrelease.bat [-x86] [-x64] [-ARM64] [-D] [-B]
17 [-o <output directory>] [-c <certificate name>]
26 without having to build it themselves.
45 and command-line logic, as well as the ability to locate and optionally
64 Before building the installer, download extra build dependencies using
76 For testing, the installer should be built with the Tools/msi/build.bat
[all …]
|
| /external/arm-trusted-firmware/docs/getting_started/ |
| D | docs-build.rst | 5 `Sphinx`_ tool to build and package the plain-text documents into HTML-formatted
14 https://www.trustedfirmware.org/docs/tf-a, if you want to view a rendered
15 copy without doing a local build.
18 -------------
20 For building a local copy of the |TF-A| documentation you will need, at minimum:
22 - Python 3 (3.5 or later)
23 - PlantUML (1.2017.15 or later)
29 ``requirements.txt`` file in the root of the ``docs`` directory. These modules
32 module versions required by |TF-A|.
35 that the working directory is ``docs``:
[all …]
|
| /external/cronet/third_party/icu/source/samples/uresb/ |
| D | readme.txt | 4 Copyright (c) 2001-2010 International Business Machines
15 uresb.sln Windows MSVC workspace. Double-click this to get started.
20 root.txt Root resource bundle
24 To Build uresb on Windows
25 1. Install and build ICU
27 3. Choose a Debug or Release build.
28 4. Build.
32 2. Add ICU's bin directory to the path, e.g.
35 3. cd into the uresb directory, e.g.
39 …WARNING: The .txt files must be in the same directory as the executable, which is not the case by …
[all …]
|
| /external/python/cpython3/Lib/distutils/command/ |
| D | install.py | 30 # The following code provides backward-compatible INSTALL_SCHEMES
46 # On POSIX-y platforms, Python will:
47 # - Build from .h files in 'headers' (only there when
49 # - Install .h files to 'include'
64 # platlibdir is available since 3.9: bpo-1294959
92 description = "install everything from build directory"
98 ('exec-prefix=', None,
99 "(Unix only) prefix for platform-specific files"),
101 "(Unix only) home directory to install under"),
104 ('install-base=', None,
[all …]
|
| /external/angle/build/ |
| D | landmines.py | 3 # Use of this source code is governed by a BSD-style license that can be
8 detects that the build should be clobbered, it will delete the contents of the
9 build directory.
12 diff between the new landmines and the old ones is non-null. At this point, the
13 build is clobbered.
16 Doing so will wipe out every output directory on every Chrome developer's
17 machine. This can be particularly problematic on Windows where the directory
18 deletion may well fail (locked files, command prompt in the directory, etc.),
21 This output directory deletion will be repeated when going back and forth across
41 Returns the absolute path to the directory containing the build directories.
[all …]
|
| /external/cronet/build/ |
| D | landmines.py | 3 # Use of this source code is governed by a BSD-style license that can be
8 detects that the build should be clobbered, it will delete the contents of the
9 build directory.
12 diff between the new landmines and the old ones is non-null. At this point, the
13 build is clobbered.
16 Doing so will wipe out every output directory on every Chrome developer's
17 machine. This can be particularly problematic on Windows where the directory
18 deletion may well fail (locked files, command prompt in the directory, etc.),
21 This output directory deletion will be repeated when going back and forth across
41 Returns the absolute path to the directory containing the build directories.
[all …]
|
| /external/bazelbuild-remote-apis/build/bazel/remote/execution/v2/ |
| D | remote_execution.proto | 7 // http://www.apache.org/licenses/LICENSE-2.0
17 package build.bazel.remote.execution.v2;
19 import "build/bazel/semver/semver.proto";
28 option csharp_namespace = "Build.Bazel.Remote.Execution.V2";
29 option go_package = "github.com/bazelbuild/remote-apis/build/bazel/remote/execution/v2;remoteexecut…
32 option java_package = "build.bazel.remote.execution.v2";
37 // [Action][build.bazel.remote.execution.v2.Action] on the remote
49 // [Command][build.bazel.remote.execution.v2.Command] to run, and the
50 // [Action][build.bazel.remote.execution.v2.Action] into the
51 // [ContentAddressableStorage][build.bazel.remote.execution.v2.ContentAddressableStorage].
[all …]
|
| /external/cronet/third_party/icu/source/data/ |
| D | icu4j-readme.txt | 4 * Copyright (C) 2008-2012, International Business Machines Corporation *
7 * 6/26/08 - Created by Brian Rower - heavy copying from ICU4J readme & others *
16 $icu4c_root is the ICU4C root directory
17 $icu4j_root is the ICU4J root directory
18 $jdk_bin is the JDK bin directory (for the jar tool)
21 Download, configure, and build ICU4C. When you configure ICU4C, you must
23 "--include_uni_core_data" to build additional required ICU4J data:
25 ICU_DATA_BUILDTOOL_OPTS=--include_uni_core_data ./runConfigureICU Linux
28 …- Add ICU_DATA_BUILDTOOL_OPTS as a system environment variable with value "--include_uni_core_data"
29 - Build $icu4c_root\source\allinone\allinone.sln in Visual Studio
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/android/ |
| D | lite_build.md | 1 # Build TensorFlow Lite for Android
3 This document describes how to build TensorFlow Lite Android library on your
4 own. Normally, you do not need to locally build TensorFlow Lite Android library.
6 …Lite AAR hosted at MavenCentral](https://search.maven.org/artifact/org.tensorflow/tensorflow-lite).
12 To use nightly snapshots, add the following repo to your root Gradle build
15 ```build
20 name 'ossrh-snapshot'
27 ## Build TensorFlow Lite locally
29 In some cases, you might wish to use a local build of TensorFlow Lite. For
34 ### Set up build environment using Docker
[all …]
|
| /external/icu/icu4c/source/data/ |
| D | icu4j-readme.txt | 4 * Copyright (C) 2008-2012, International Business Machines Corporation *
7 * 6/26/08 - Created by Brian Rower - heavy copying from ICU4J readme & others *
16 $icu4c_root is the ICU4C root directory
17 $icu4j_root is the ICU4J root directory
18 $jdk_bin is the JDK bin directory (for the jar tool)
21 Download, configure, and build ICU4C. When you configure ICU4C, you must
23 "--include_uni_core_data" to build additional required ICU4J data:
25 ICU_DATA_BUILDTOOL_OPTS=--include_uni_core_data ./runConfigureICU Linux
28 …- Add ICU_DATA_BUILDTOOL_OPTS as a system environment variable with value "--include_uni_core_data"
29 - Build $icu4c_root\source\allinone\allinone.sln in Visual Studio
[all …]
|