Searched +full:- +full:- +full:build +full:- +full:and +full:- +full:test (Results 1 – 25 of 1120) sorted by relevance
12345678910>>...45
| /external/openthread/third_party/mbedtls/repo/tests/scripts/ |
| D | all.sh | 6 # SPDX-License-Identifier: Apache-2.0
12 # http://www.apache.org/licenses/LICENSE-2.0
17 # See the License for the specific language governing permissions and
27 # -------
32 # ---------------
34 # Warning: the test is destructive. It includes various build modes and
35 # configurations, and can and will arbitrarily change the current CMake
40 # After running this script, the CMake cache will be lost and CMake
44 # * Basic Unix tools (Windows users note: a Unix-style find must be before
49 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/tools/buildgen/ |
| D | extract_metadata_from_bazel_xml.py | 8 # http://www.apache.org/licenses/LICENSE-2.0
13 # See the License for the specific language governing permissions and
16 # Script to extract build metadata from bazel BUILD.
17 # To avoid having two sources of truth for the build metadata (build
19 # of bazel BUILD files and generates a YAML file (currently called
20 # build_autogenerated.yaml). The format and semantics of the generated YAML files
21 # is chosen to match the format of a "build.yaml" file, which used
22 # to be build the source of truth for gRPC build before bazel became
23 # the primary build system.
24 # A good basic overview of the "build.yaml" format is available here:
[all …]
|
| /external/mbedtls/tests/scripts/ |
| D | all.sh | 6 # SPDX-License-Identifier: Apache-2.0
12 # http://www.apache.org/licenses/LICENSE-2.0
17 # See the License for the specific language governing permissions and
27 # -------
32 # ---------------
34 # Warning: the test is destructive. It includes various build modes and
35 # configurations, and can and will arbitrarily change the current CMake
40 # After running this script, the CMake cache will be lost and CMake
44 # * Basic Unix tools (Windows users note: a Unix-style find must be before
49 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
[all …]
|
| /external/armnn/ |
| D | BuildGuideAndroidNDK.md | 1 # How to use the Android NDK to build Arm NN
3 - [Introduction](#introduction)
4 - [Initial Setup](#initial-setup)
5 - [Download the Android NDK and make a standalone toolchain](#download-the-android-ndk-and-make-a-s…
6 - [Install Cmake](#install-cmake)
7 - [Build Flatbuffers](#build-flatbuffers)
8 - [Download Arm NN](#download-arm-nn)
9 - [Get And Build TFLite](#get-and-build-tflite)
10 - [Build Arm Compute Library](#build-arm-compute-library)
11 - [Build Arm NN](#build-arm-nn)
[all …]
|
| /external/tinyxml2/.github/workflows/ |
| D | test.yml | 1 name: Test
4 test:
7 fail-fast: false
9 os: [ windows-2019, macos-10.15, ubuntu-20.04 ]
12 - os: windows-2019
17 - os: ubuntu-20.04
20 - os: macos-10.15
23 - cmake: 3.15
25 - cmake: 3.x
31 runs-on: ${{ matrix.os }}
[all …]
|
| /external/libaom/ |
| D | README.md | 6 1. [Building the lib and applications](#building-the-library-and-applications)
7 - [Prerequisites](#prerequisites)
8 - [Get the code](#get-the-code)
9 - [Basics](#basic-build)
10 - [Configuration options](#configuration-options)
11 - [Dylib builds](#dylib-builds)
12 - [Debugging](#debugging)
13 - [Cross compiling](#cross-compiling)
14 - [Sanitizer support](#sanitizers)
15 - [MSVC builds](#microsoft-visual-studio-builds)
[all …]
|
| /external/fsverity-utils/scripts/ |
| D | run-tests.sh | 2 # SPDX-License-Identifier: MIT
5 # Use of this source code is governed by an MIT-style
10 # Test script for fsverity-utils. Runs 'make check' in lots of configurations,
11 # runs static analysis, and does a few other tests.
13 # Note: for more test coverage, in addition to running this script, also build
14 # fsverity-utils into a kvm-xfstests test appliance and run
15 # 'kvm-xfstests -c ext4,f2fs -g verity'
17 set -e -u -o pipefail
31 TMPDIR=$(mktemp -d -t libfsverity_test.XXXXXXXXX)
32 trap 'rm -r "$TMPDIR"' EXIT
[all …]
|
| /external/e2fsprogs/.github/workflows/ |
| D | ci.yml | 4 DEF_CFLAGS: -O2 -g -Wall
7 gcc-build-and-test:
8 name: Build and test with gcc
9 runs-on: ubuntu-latest
11 - uses: actions/checkout@v3
12 - run: ./configure CC=gcc CFLAGS="$DEF_CFLAGS"
13 - run: make -j8 check V=1 CFLAGS_WARN="-Werror"
14 - run: make -j8 install V=1 DESTDIR=$PWD/installdir
15 - run: make -j8 uninstall V=1 DESTDIR=$PWD/installdir
17 clang-build-and-test:
[all …]
|
| /external/deqp/external/openglcts/ |
| D | README.md | 1 OpenGL and OpenGL ES 2.0/3.X Conformance Test Instructions
4 This document describes how to build, port, and run the OpenGL and OpenGL ES
5 2.0/3.X conformance tests, and how to verify and submit test results.
8 Up-to-date documentation for dEQP is available at:
10 * [The VK-GL-CTS wiki for Khronos members](https://gitlab.khronos.org/Tracker/vk-gl-cts/wikis/home)
11 * [The VK-GL-CTS wiki for non-Khronos members](https://github.com/KhronosGroup/VK-GL-CTS/wiki)
15 ------------------------
16 - [Test History](#test-history)
17 - [Introduction](#introduction)
18 - [Test Environment Requirements](#test-environment-requirements)
[all …]
|
| /external/cronet/buildtools/third_party/libc++/trunk/docs/ |
| D | TestingLibcxx.rst | 13 libc++ uses LIT to configure and run its tests.
15 The primary way to run the libc++ tests is by using ``make check-cxx``.
18 configurations it is important to customize the way LIT builds and runs
20 test libc++.
27 -----
29 After building libc++, you can run parts of the libc++ test suite by simply
30 running ``llvm-lit`` on a specified test or directory. If you're unsure
32 ``cxx-test-depends`` target. For example:
34 .. code-block:: bash
36 $ cd <monorepo-root>
[all …]
|
| /external/rust/beto-rust/nearby/scripts/ |
| D | build-script.sh | 7 # http://www.apache.org/licenses/LICENSE-2.0
12 # See the License for the specific language governing permissions and
16 # specific components of the beto-rust repo. To load these into your environment
17 # run `source ./scripts/build-script.sh` Then run the functions from root
18 # This can also be sourced to help when writing further build scripts
20 export SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )
24 set -e
25 …-c "Google LLC" -l apache -ignore=**/android/build/** -ignore=target/** -ignore=**/target/** -igno…
28 # Checks the workspace 3rd party crates and makes sure they have a valid license
30 set -e
[all …]
|
| /external/cronet/testing/android/docs/ |
| D | android_test_instructions.md | 1 # Building and Running Android Tests
11 Running tests requires root access, which requires using a userdebug build on
14 To use a userdebug build, see
15 [Running Builds](https://source.android.com/setup/build/running.html). Googlers
19 the test APKs like "adb: error: failed to copy" and
28 third_party/android_sdk/public/platform-tools/adb
36 * Tap 10 times on "Build number"
39 * Un-check "Verify apps over USB".
44 stayon usb` Or do this manually on the device: Settings -> Developer options ->
54 one](http://www.samsungmobileusa.com/simulators/ATT_GalaxyMega/mobile/screens/06-02_12.jpg),
[all …]
|
| /external/cronet/third_party/googletest/src/docs/ |
| D | quickstart-bazel.md | 3 This tutorial aims to get you up and running with GoogleTest using the Bazel
4 build system. If you're using GoogleTest for the first time or need a refresher,
13 * [Bazel](https://bazel.build/), the preferred build system used by the
20 [Bazel installation guide](https://docs.bazel.build/versions/main/install.html).
29 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
31 software you want to build. Each workspace directory has a text file named
33 dependencies required to build the outputs.
41 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
43 [Bazel external dependency](https://docs.bazel.build/versions/main/external.html)
45 [`http_archive` rule](https://docs.bazel.build/versions/main/repo/http.html#http_archive).
[all …]
|
| /external/autotest/server/site_tests/provision_CheetsUpdate/ |
| D | provision_CheetsUpdate.py | 2 # Use of this source code is governed by a BSD-style license that can be
15 from autotest_lib.server import test
18 # 2 & 4 are default partitions, and the system boots from one of them.
26 class provision_CheetsUpdate(test.test):
28 Update Android build On the target DUT.
30 This test is designed for ARC++ Treehugger style CQ to update Android image
44 Download the Android test build from the dev server.
46 @param android_build: Android build to test.
47 @param ds: Dev server instance for downloading the test build.
50 logging.info('Generated build name: %s', build_filename)
[all …]
|
| /external/fmtlib/test/ |
| D | CMakeLists.txt | 1 #------------------------------------------------------------------------------
2 # Build the google test library
4 # We compile Google Test ourselves instead of using pre-compiled libraries.
5 # See the Google Test FAQ "Why is it not recommended to install a
6 # pre-compiled copy of Google Test (for example, into /usr/local)?"
9 gmock-gtest-all.cc gmock/gmock.h gtest/gtest.h gtest/gtest-spi.h)
30 target_compile_options(gmock PUBLIC -Wno-deprecated-declarations)
43 #------------------------------------------------------------------------------
44 # Build the actual library tests
46 set(TEST_MAIN_SRC test-main.cc gtest-extra.cc gtest-extra.h util.cc)
[all …]
|
| /external/pigweed/docs/ |
| D | getting_started.rst | 1 .. _docs-getting-started:
10 This documentation and the `sample project
24 in-depth guide below, starting at :ref:`prerequisites`. The express setup
27 #. **Host** - Mac, Linux, or Windows. Builds and runs tests
28 #. **Device/STM32F429** - Build only; Optionally, the STM32F429I-DISC1 kit to
30 #. **Docs** - Builds the Pigweed docs
34 #. Make sure you have Git and Python installed and on your path.
36 #. Clone Pigweed and bootstrap the environment (compiler setup & more). **Be
37 patient, this step downloads ~1GB of LLVM, GCC, and other tooling**.
49 #. Configure the GN build.
[all …]
|
| /external/googletest/docs/ |
| D | quickstart-bazel.md | 3 This tutorial aims to get you up and running with GoogleTest using the Bazel
4 build system. If you're using GoogleTest for the first time or need a refresher,
13 * [Bazel](https://bazel.build/), the preferred build system used by the
20 [Bazel installation guide](https://docs.bazel.build/versions/master/install.html).
29 [Bazel workspace](https://docs.bazel.build/versions/master/build-ref.html#workspace)
31 software you want to build. Each workspace directory has a text file named
33 dependencies required to build the outputs.
41 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
43 [Bazel external dependency](https://docs.bazel.build/versions/master/external.html)
45 [`http_archive` rule](https://docs.bazel.build/versions/master/repo/http.html#http_archive).
[all …]
|
| /external/ltp/testcases/open_posix_testsuite/Documentation/ |
| D | HOWTO_RunTests | 4 3. Building and Running the Tests
7 ------------
8 This document describes how to run the tests in the POSIX Test Suite.
10 Our framework currently has the ability to build and run conformance,
11 functional, and stress tests. All tests are built with make all, but
12 certain care should be used when running the stress test suite as the
16 ----------------------------------------------------
19 The build and execution process varies for conformance tests.
21 For definitions tests, the build and execution process is the same since
22 the pass/fail criterion is determine by whether or not the test compiles.
[all …]
|
| /external/OpenCSD/decoder/docs/ |
| D | build_libs.md | 1 Building and using the Library {#build_lib}
4 @brief How to build the library and test programs and include the library in an application
7 ----------------
9 The current makefiles and build projects support building the library on:
10 - Linux and Windows, x86 or x64 hosts.
11 - ARM linux - AArch32 and AArch64
12 - ARM aarch32 and aarch64 libs, x-compiled on x86/64 hosts.
15 `/usr/lib/` area in Linux, and will soon be available as a package from Linux Distros.
18 --------------------
20 The library and test programs are built from the library `./build/<platform>` directory, where
[all …]
|
| /external/openthread/third_party/nlbuild-autotools/repo/examples/ |
| D | configure.ac | 1 # -*- Autoconf -*-
5 # Copyright 2016-2018 Nest Labs Inc. All Rights Reserved.
11 # http://www.apache.org/licenses/LICENSE-2.0
16 # See the License for the specific language governing permissions and
35 m4_esyscmd([@NLBUILD_AUTOTOOLS_STEM@/scripts/mkversion -b `cat .default-version` .]),
40 # Tell the rest of the build system the absolute path where the
41 # nlbuild-autotools repository is rooted at.
47 # @PACKAGE_SHORT_UPPER@ interface current, revision, and age versions.
68 # Tell autoconf where to find auxilliary build tools (e.g. config.guess,
69 # install-sh, missing, etc.)
[all …]
|
| /external/angle/doc/ |
| D | DebuggingTips.md | 3 There are many ways to debug ANGLE using generic or platform-dependent tools. Here is a list of tips
10 inserts a driver shim using `LD_PRELOAD` that records the command and then forwards it to the OpenGL
14 the entry point calls intended for ANGLE and reroutes them to the OpenGL driver. In order to avoid
17 1. Link your application against the static ANGLE libraries (libGLESv2_static and libEGL_static) so
23 `ldconfig -p | grep libGL`.
34 # edit samples/BUILD.gn and append "_static" to "angle_util", "libEGL", "libGLESv2"
35 ninja -C out/Debug
37 apitrace trace -o mytrace ./out/Debug/hello_triangle
43 Normally, ANGLE only logs errors and warnings (e.g. to Android logcat). General logging, or
49 To log all GLES and EGL commands submitted by an application, including the following flag:
[all …]
|
| /external/gemmlowp/ |
| D | README.md | 1 # gemmlowp: a small self-contained low-precision GEMM library
3 [](http://travis-ci.org/google/gem…
9 [doc/low-precision.md](doc/low-precision.md)
22 gemmlowp-related discussion, about either development or usage, is welcome on
29 Should be portable to any platform with some C++11 and POSIX support, while we
39 * pthreads (for multi-threaded operation and for profiling).
40 * sysconf (for multi-threaded operation to detect number of cores; may be
45 * Architecture-specific code paths use intrinsics or inline assembly. See
46 "Architecture-specific optimized code paths" below.
48 ## Architecture-specific optimized code paths
[all …]
|
| /external/openthread/ |
| D | configure.ac | 1 # -*- Autoconf -*-
8 # Redistribution and use in source and binary forms, with or without
11 # notice, this list of conditions and the following disclaimer.
13 # notice, this list of conditions and the following disclaimer in the
14 # documentation and/or other materials provided with the distribution.
19 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
20 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
41 … m4_esyscmd([third_party/nlbuild-autotools/repo/scripts/mkversion -b `cat .default-version` .]),
[all …]
|
| /external/angle/third_party/abseil-cpp/CMake/ |
| D | README.md | 1 # Abseil CMake Build Instructions
3 Abseil comes with a CMake build script ([CMakeLists.txt](../CMakeLists.txt))
4 that can be used on a wide range of platforms ("C" stands for cross-platform.).
8 CMake works by generating native makefiles or build projects that can
18 …m/google/googletest/blob/master/googletest/README.md#incorporating-into-an-existing-cmake-project>)
20 ### Step-by-Step Instructions
22 1. If you want to build the Abseil tests, integrate the Abseil dependency
23 [Google Test](https://github.com/google/googletest) into your CMake
25 `-DBUILD_TESTING=OFF` or `-DABSL_BUILD_TESTING=OFF` when configuring your
28 2. Download Abseil and copy it into a subdirectory in your CMake project or add
[all …]
|
| /external/tensorflow/third_party/absl/abseil-cpp/CMake/ |
| D | README.md | 1 # Abseil CMake Build Instructions
3 Abseil comes with a CMake build script ([CMakeLists.txt](../CMakeLists.txt))
4 that can be used on a wide range of platforms ("C" stands for cross-platform.).
8 CMake works by generating native makefiles or build projects that can
18 …m/google/googletest/blob/master/googletest/README.md#incorporating-into-an-existing-cmake-project>)
20 ### Step-by-Step Instructions
22 1. If you want to build the Abseil tests, integrate the Abseil dependency
23 [Google Test](https://github.com/google/googletest) into your CMake
25 `-DBUILD_TESTING=OFF` or `-DABSL_BUILD_TESTING=OFF` when configuring your
28 2. Download Abseil and copy it into a subdirectory in your CMake project or add
[all …]
|
12345678910>>...45