Home
last modified time | relevance | path

Searched +full:- +full:- +full:build +full:- +full:and +full:- +full:test (Results 1 – 25 of 1315) sorted by relevance

12345678910>>...53

/external/libva-utils/test/gtest/
DREADME.md2 ### Generic Build Instructions ###
6 To build Google Test and your tests that use it, you need to tell your
7 build system where to find its headers and source files. The exact
8 way to do it depends on which build system you use, and is usually
11 #### Build #### subsubsection
13 Suppose you put Google Test in directory `${GTEST_DIR}`. To build it,
14 create a library build target (or a project as called by Visual Studio
15 and Xcode) to compile
17 ${GTEST_DIR}/src/gtest-all.cc
19 with `${GTEST_DIR}/include` in the system header search path and `${GTEST_DIR}`
[all …]
/external/mbedtls/tests/scripts/
Dall.sh6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
15 # -------
20 # ---------------
22 # Warning: the test is destructive. It includes various build modes and
23 # configurations, and can and will arbitrarily change the current CMake
28 # After running this script, the CMake cache will be lost and CMake
32 # * Basic Unix tools (Windows users note: a Unix-style find must be before
37 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
39 # * arm-gcc and mingw-gcc
40 # * ArmCC 5 and ArmCC 6, unless invoked with --no-armcc
[all …]
/external/apache-xml/test/java/xdocs/sources/tests/
Dgetstarted.xml3 <!--
12 * http://www.apache.org/licenses/LICENSE-2.0
17 * See the License for the specific language governing permissions and
19 -->
24 <li><link anchor="how-to-build">Building the Tests</link></li>
30 <jump href="http://xml.apache.org/xalan-j/readme.html#build">building Xalan-J</jump> and with
32 <p>Set JAVA_HOME, and have your classes.zip or tools.jar in the CLASSPATH.</p>
33 <p>Here are some sample commands to build and run tests:</p>
35 …<br/><code>checkout xml-xalan/java </code> Get the Xalan-J code (or simply get a nightly build or…
36 <br/><code>cd xml-xalan/java </code>
[all …]
/external/grpc-grpc/tools/buildgen/
Dextract_metadata_from_bazel_xml.py8 # 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/rust/android-crates-io/crates/grpcio-sys/grpc/tools/buildgen/
Dextract_metadata_from_bazel_xml.py8 # 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/openthread/third_party/mbedtls/repo/tests/scripts/
Dall.sh6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
15 # -------
20 # ---------------
22 # Warning: the test is destructive. It includes various build modes and
23 # configurations, and can and will arbitrarily change the current CMake
28 # After running this script, the CMake cache will be lost and CMake
32 # * Basic Unix tools (Windows users note: a Unix-style find must be before
37 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
39 # * arm-gcc and mingw-gcc
40 # * ArmCC 5 and ArmCC 6, unless invoked with --no-armcc
[all …]
/external/tinyxml2/.github/workflows/
Dtest.yml1 name: Test
4 test:
7 fail-fast: false
9 os: [ windows-2019, macos-latest, ubuntu-20.04 ]
12 - os: windows-2019
17 - os: ubuntu-20.04
20 - os: macos-latest
23 - cmake: 3.15
25 - cmake: 3.x
31 runs-on: ${{ matrix.os }}
[all …]
/external/armnn/
DBuildGuideAndroidNDK.md1 # 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/fsverity-utils/scripts/
Drun-tests.sh2 # 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/sdv/vsomeip/test/
Dreadme.txt1 Configuration Test
2 ------------------
3 To start the configuration test from the build directory do:
5 ./configuration-test -someip ../config/vsomeip-test.json
9 2015-02-10 08:47:31.503874 [info] Test "HOST ADDRESS" succeeded.
10 2015-02-10 08:47:31.507609 [info] Test "HAS CONSOLE" succeeded.
11 2015-02-10 08:47:31.507865 [info] Test "HAS FILE" succeeded.
12 2015-02-10 08:47:31.508001 [info] Test "HAS DLT" succeeded.
13 2015-02-10 08:47:31.508143 [info] Test "LOGFILE" succeeded.
14 2015-02-10 08:47:31.508315 [info] Test "LOGLEVEL" succeeded.
[all …]
/external/fmtlib/test/
DCMakeLists.txt5 set(TEST_MAIN_SRC test-main.cc gtest-extra.cc gtest-extra.h util.cc)
6 add_library(test-main STATIC ${TEST_MAIN_SRC})
7 target_include_directories(test-main PUBLIC
9 target_link_libraries(test-main gtest fmt)
11 # Adds a test.
19 set(libs gtest fmt-header-only)
21 set(PEDANTIC_COMPILE_FLAGS ${PEDANTIC_COMPILE_FLAGS} -Wno-weak-vtables)
24 set(libs test-main test-module)
25 set_source_files_properties(${name}.cc PROPERTIES OBJECT_DEPENDS test-module)
27 set(libs test-main fmt)
[all …]
/external/libdisplay-info/
D.gitlab-ci.yml2 - project: 'freedesktop/ci-templates'
5 - '/templates/ci-fairy.yml'
6 - '/templates/alpine.yml'
8 # When updating the prepare-container step, make sure to bump
11 # $ git push -f -o ci.variable="FDO_FORCE_REBUILD=1"
13 FDO_UPSTREAM_REPO: 'emersion/libdisplay-info'
14 FDO_DISTRIBUTION_TAG: '2024-06-07.0'
18 - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
19 - if: $CI_PIPELINE_SOURCE == 'push'
22 - "Contribution checks"
[all …]
/external/libaom/
DREADME.md6 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/e2fsprogs/.github/workflows/
Dci.yml4 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/
DREADME.md1 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 - [OpenGL and OpenGL ES 2.0/3.X Conformance Test Instructions](#opengl-and-opengl-es-203x-conforman…
17 - [Contents](#contents)
18 - [Test History](#test-history)
[all …]
/external/cronet/tot/third_party/googletest/src/docs/
Dquickstart-bazel.md3 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/) 7.0 or higher, the preferred build system used
20 [Bazel installation guide](https://bazel.build/install).
28 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
30 software you want to build. Each workspace directory has a text file named
32 dependencies required to build the outputs.
42 [Bazel Central Registry](https://registry.bazel.build/modules/googletest). To do
50 # https://registry.bazel.build/modules/googletest
54 Now you're ready to build C++ code that uses GoogleTest.
[all …]
/external/cronet/stable/third_party/googletest/src/docs/
Dquickstart-bazel.md3 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/) 7.0 or higher, the preferred build system used
20 [Bazel installation guide](https://bazel.build/install).
28 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
30 software you want to build. Each workspace directory has a text file named
32 dependencies required to build the outputs.
42 [Bazel Central Registry](https://registry.bazel.build/modules/googletest). To do
50 # https://registry.bazel.build/modules/googletest
54 Now you're ready to build C++ code that uses GoogleTest.
[all …]
/external/googletest/docs/
Dquickstart-bazel.md3 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/) 7.0 or higher, the preferred build system used
20 [Bazel installation guide](https://bazel.build/install).
28 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
30 software you want to build. Each workspace directory has a text file named
32 dependencies required to build the outputs.
42 [Bazel Central Registry](https://registry.bazel.build/modules/googletest). To do
50 # https://registry.bazel.build/modules/googletest
54 Now you're ready to build C++ code that uses GoogleTest.
[all …]
/external/pytorch/.github/workflows/
D_win-build.yml1 name: windows-build
6 build-environment:
9 description: Top-level label for what's being built/tested.
10 cuda-version:
13 description: What CUDA version to build with, "cpu" for none.
14 build-with-debug:
18 description: If set, build in debug mode.
19 sync-tag:
25 job with the same `sync-tag` is identical.
26 test-matrix:
[all …]
/external/ltp/testcases/open_posix_testsuite/Documentation/
DHOWTO_RunTests4 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/python/cpython3/Android/
DREADME.md11 First, make sure you have all the usual tools and libraries needed to build
19 * Create a directory `android-sdk/cmdline-tools`, and unzip the command line
21 * Rename `android-sdk/cmdline-tools/cmdline-tools` to
22 `android-sdk/cmdline-tools/latest`.
23 * `export ANDROID_HOME=/path/to/android-sdk`
37 cross-build where you use a "build" Python (for your development machine) to
40 The easiest way to do a build is to use the `android.py` script. You can either
41 have it perform the entire build process from start to finish in one step, or
42 you can do it in discrete steps that mirror running `configure` and `make` for
48 ./android.py configure-build
[all …]
/external/libva-utils/test/gtest/docs/
DXcodeGuide.md7 Here is the quick guide for using Google Test in your Xcode project.
9 …using this command: `svn checkout http://googletest.googlecode.com/svn/trunk/ googletest-read-only`
10 …1. Open up the `gtest.xcodeproj` in the `googletest-read-only/xcode/` directory and build the gtes…
12 …1. Add the gtest.framework to your project and add it to the "Link Binary with Libraries" build ph…
13 1. Add your unit test source code to the "Compile Sources" build phase of "UnitTests"
14 …1. Edit the "UnitTests" executable and add an environment variable named "DYLD\_FRAMEWORK\_PATH" w…
15 1. Build and Go
21 …available in a tagged release of Google Test, it is only available in the trunk. As explained at t…
24 svn checkout http://googletest.googlecode.com/svn/trunk/ googletest-read-only
27 …Test as an external dependency to your own Subversion repository. By following this approach, ever…
[all …]
/external/coreboot/Documentation/technotes/
D2021-05-code-coverage.md1 # Unit Test Code Coverage
4 code in the coreboot library are covered by unit tests, and allows a test
5 author to see where they need to add test cases for additional coverage.
10 Enable code coverage in your unit test build by setting the environment
12 `make` command, e.g. `COV=1 make unit-tests`.
14 The build output directory is either `build/tests` or `build/coverage`,
17 All of the unit test targets are available with and without `COV=1`
18 * `clean-unit-tests`
19 * `build-unit-tests`
20 * `run-unit-tests`
[all …]
/external/pytorch/.github/scripts/
Dtest_filter_test_configs.py25 "pull / mock-platform-1": [
30 "mock-platform-1",
33 "trunk / mock-platform-2 / build": [
38 "mock-platform-2",
39 "build",
41 "periodic / mock-platform-3 / test": [
46 "mock-platform-3",
47 "test",
49 "pull / mock-platform-4 / build-and-test": [
54 "mock-platform-4",
[all …]
/external/wayland/
D.gitlab-ci.yml1 # 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
5 # image is built which contains the core distribution, the toolchain, and
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.
17 # The final stage is used to expose documentation and coverage information,
21 # Apart from the 'variables', 'include', and 'stages' top-level anchors,
27 # variables prefixed with FDO_ and templates prefixed by .fdo are provided
[all …]

12345678910>>...53