Searched +full:build +full:- +full:and +full:- +full:test (Results 1 – 25 of 1120) sorted by relevance
12345678910>>...45
| /third_party/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 …]
|
| /third_party/mbedtls/tests/scripts/ |
| D | all.sh | 6 # 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 …]
|
| /third_party/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 …]
|
| /third_party/icu/docs/processes/release/tasks/ |
| D | healthy-code.md | 1 ---
7 ---
9 <!--
10 © 2021 and later: Unicode, Inc. and others.
12 -->
18 {: .no_toc .text-delta }
23 ---
33 See Normalizer2 for an example declaration and implementation that satisfies the
34 virtual-function override without adding new ClassID support.
36 We do need to keep and add "poor man's RTTI" in old classes, and in new classes
[all …]
|
| D | integration.md | 1 ---
7 ---
9 <!--
10 © 2021 and later: Unicode, Inc. and others.
12 -->
18 {: .no_toc .text-delta }
23 ---
28 special jar file (icu4j-localespi.jar) implementing the locale service provider
31 The test case for the ICU4J locale service provider requires JRE 6 or later
33 up ( necessary. To run the test cases, use ant with the top-level build.xml with
[all …]
|
| /third_party/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 …]
|
| /third_party/astc-encoder/Docs/ |
| D | Testing.md | 4 check source code changes to the compressor. It must be noted that this test
5 suite is relatively limited in scope and does not cover every feature or
10 Running the tests requires Python 3.7 to be installed on the host machine, and
11 an `astcenc-avx2` release build to have been previously compiled and installed
13 can be achieved by configuring the CMake build using the install prefix
14 `-DCMAKE_INSTALL_PREFIX=../` and then running a build with the `install` build
20 using the `googletest` framework and integrated in the CMake "CTest" test
23 To build unit tests pull the `googletest` git submodule and add
24 `-DASTCENC_UNITTEST=ON` to the CMake command line when configuring.
26 To run unit tests use the CMake `ctest` utility from your build directory after
[all …]
|
| /third_party/vk-gl-cts/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 - [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 …]
|
| /third_party/benchmark/ |
| D | README.md | 3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …test-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://git…
31 To get started, see [Requirements](#requirements) and
32 [Installation](#installation). See [Usage](#usage) for a full example and the
35 It may also help to read the [Google Test documentation](https://github.com/google/googletest/blob/…
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++11 to build,
54 including compiler and standard library support.
56 The following minimum versions are required to build the library:
[all …]
|
| /third_party/libuv/ |
| D | ChangeLog | 7 * build: disable windows asan buildbot (Ben Noordhuis)
9 * test: don't run tcp_writealot under msan (Ben Noordhuis)
11 * build,win: remove extraneous -lshell32 (Ben Noordhuis)
19 * test: check if ipv6 link-local traffic is routable (Ben Noordhuis)
35 * test_fs.c: Fix issue on 32-bit systems using btrfs (Stephen Gallagher)
37 * misc: ignore libuv-release-tool files (Jameson Nash)
45 * test: skip tcp-write-in-a-row on IBM i (Abdirahim Musse)
47 * build,win: work around missing uuid.dll on MinGW (Anton Bachin)
59 * build: add .cache clangd folder to .gitignore (Juan José Arboleda)
61 * unix: support full TCP keep-alive on Solaris (Andy Pan)
[all …]
|
| D | README.md | 5 libuv is a multi-platform support library with a focus on asynchronous I/O. It
8 [uvloop](https://github.com/MagicStack/uvloop), and [others](https://github.com/libuv/libuv/blob/v1…
12 * Full-featured event loop backed by epoll, kqueue, IOCP, event ports.
14 * Asynchronous TCP and UDP sockets
18 * Asynchronous file and file system operations
34 * Threading and synchronization primitives
39 scheme. The API change and backwards compatibility rules are those indicated by
42 The ABI/API changes can be tracked [here](http://abi-laboratory.pro/tracker/timeline/libuv/).
46 libuv is licensed under the MIT license. Check the [LICENSE](LICENSE) and
47 [LICENSE-extra](LICENSE-extra) files.
[all …]
|
| /third_party/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://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.
40 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
42 [Bazel external dependency](https://docs.bazel.build/versions/main/external.html)
44 [`http_archive` rule](https://docs.bazel.build/versions/main/repo/http.html#http_archive).
[all …]
|
| /third_party/skia/m133/modules/canvaskit/ |
| D | README.md | 4 test dependencies. Recent installations of Node have npm as well.
8 To build with GN, you need to have followed the instructions to download Skia and its deps
11 To compile CanvasKit, you will first need to [download and activate `emscripten`][1] using the
12 script in `//bin/activate-emsdk` (or `//tools/git-sync-deps` which also calls activate-emsdk).
13 This places the associated files in `//third_party/externals/emsdk` and the GN[2] build scripts
18 `//modules/canvaskit/BUILD.gn`.
25 can fail with errors about SSL certificates. <https://github.com/emscripten-core/emsdk/pull/273>
27 See also <https://github.com/emscripten-core/emscripten/issues/9036#issuecomment-532092743>
30 # Compile and Run Local Example
33 # The following installs all npm dependencies and only needs to be when setting up
[all …]
|
| /third_party/grpc/tools/remote_build/ |
| D | README.md | 3 This allows you to spawn gRPC C/C++ remote build and tests from your workstation with
7 remote build and execution cluster), others will need to rely on local test runs
8 and tests run by Kokoro CI.
13 - See [Installing Bazel](https://docs.bazel.build/versions/master/install.html) for instructions ho…
15 - Setup Application Default Credentials (ADC) for running remote builds by following the ["Set cred…
18 ## Running remote build manually from dev workstation
20 …build & execution platform. If you want to run tests on linux, you need to run bazel from a linux …
27 bazel --bazelrc=tools/remote_build/linux.bazelrc test --config=opt //test/...
33 bazel --bazelrc=tools/remote_build/linux.bazelrc test --config=asan //test/...
36 …Build Event Protocol upload failure (e.g. `ERROR: The Build Event Protocol upload failed: All retr…
[all …]
|
| /third_party/musl/libc-test/ |
| D | README | 1 libc-test is developed as part of the musl project
2 http://www.musl-libc.org/
7 build and run tests:
12 make builds all test binaries and runs them to create
13 a REPORT file that contains all build and runtime errors
14 (this means that make does not stop at build failures)
20 - tests should be easy to run and build even a single test in isolation
21 (so test should be self contained if possible)
22 - failure of one test should not interfere with others
23 (build failure, crash or unexpected results are all failures)
[all …]
|
| /third_party/rust/rust/src/etc/completions/ |
| D | x.py.fish | 1 complete -c x.py -n "__fish_use_subcommand" -l config -d 'TOML configuration file for build' -r -F
2 complete -c x.py -n "__fish_use_subcommand" -l build-dir -d 'Build directory, overrides `build.buil…
3 complete -c x.py -n "__fish_use_subcommand" -l build -d 'build target of the stage0 compiler' -r -f
4 complete -c x.py -n "__fish_use_subcommand" -l host -d 'host targets to build' -r -f
5 complete -c x.py -n "__fish_use_subcommand" -l target -d 'target targets to build' -r -f
6 complete -c x.py -n "__fish_use_subcommand" -l exclude -d 'build paths to exclude' -r -F
7 complete -c x.py -n "__fish_use_subcommand" -l rustc-error-format -r -f
8 complete -c x.py -n "__fish_use_subcommand" -l on-fail -d 'command to run on failure' -r -f -a "(__…
9 …-c x.py -n "__fish_use_subcommand" -l stage -d 'stage to build (indicates compiler to use/test, e.…
10 … -c x.py -n "__fish_use_subcommand" -l keep-stage -d 'stage(s) to keep without recompiling (pass m…
[all …]
|
| /third_party/libcoap/ |
| D | configure.ac | 3 # Copyright (C) 2010-2023 Olaf Bergmann <bergmann@tzi.org>
4 # Copyright (C) 2015-2018 Carsten Schoenert <c.schoenert@t-online.de>
5 # Copyright (C) 2018-2023 Jon Shallow <supjps-libcoap@jpshallow.com>
7 # SPDX-License-Identifier: BSD-2-Clause
20 # define an appending release state if needed, for example for pre-releases
27 AC_INIT([libcoap], [libcoap_version], [libcoap-developers@lists.sourceforge.net], [libcoap], [https…
29 AM_INIT_AUTOMAKE([1.10 -Wall no-define no-dist-gzip dist-bzip2])
50 # enable the automatically build of shared and static libraries
56 # To set the version of the library, libtool provides the -version-info #
58 # respectively, current, revision and age. Both their name and their behavior, #
[all …]
|
| /third_party/skia/third_party/externals/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 project. To disable Abseil test…
24 `-DBUILD_TESTING=OFF` when configuring your project with CMake.
26 2. Download Abseil and copy it into a subdirectory in your CMake project or add
[all …]
|
| /third_party/skia/third_party/externals/harfbuzz/ |
| D | TESTING.md | 1 ## Build and Test
4 meson build
5 ninja -Cbuild
6 meson test -Cbuild
12 meson test -Cbuild --gdb testname
15 ## Build and Run
18 Values defined in `hb-debug.hh`.
21 CPPFLAGS='-DHB_DEBUG_SUBSET=100' meson setup build --reconfigure
22 meson test -C build
28 meson setup build -Db_sanitize=address --reconfigure
[all …]
|
| /third_party/protobuf/cmake/ |
| D | README.md | 1 This directory contains *CMake* files that can be used to build protobuf.
4 [Git](http://git-scm.com), and [Abseil](https://github.com/abseil/abseil-cpp)
6 and newer on both [Windows](#windows-builds) and [Linux](#linux-builds).
8 Most of the instructions will be given using CMake's command-line interface, but
20 cmake . -DCMAKE_CXX_STANDARD=14
21 cmake --build .
24 will build protobuf using C++14 (see [CXX_STANDARD](https://cmake.org/cmake/help/latest/prop_tgt/CX…
28 On Windows, you can build the project from *Command Prompt* and using an
60 Optionally, you will want to download [ninja](https://ninja-build.org/) and add it to your *PATH* v…
75 C:\Path\to\src> git clone -b [release_tag] https://github.com/protocolbuffers/protobuf.git
[all …]
|
| /third_party/mbedtls/ |
| D | README.md | 4 …mplements cryptographic primitives, X.509 certificate manipulation and the SSL/TLS and DTLS protoc…
6 Mbed TLS includes a reference implementation of the [PSA Cryptography API](#psa-cryptography-api). …
9 -------------
11 …build out of the box on most systems. Some platform specific options are available in the fully do…
13 …ing conventional environment variables such as `CC` and `CFLAGS` when using the Make and CMake bui…
15 We provide some non-standard configurations focused on specific use cases in the `configs/` directo…
18 -------------
20 The main Mbed TLS documentation is available via [ReadTheDocs](https://mbed-tls.readthedocs.io/).
22 …or the PSA Cryptography API is available [on GitHub](https://arm-software.github.io/psa-api/crypto…
24 To generate a local copy of the library documentation in HTML format, tailored to your compile-time…
[all …]
|
| /third_party/openssl/ |
| D | INSTALL.md | 1 Build and Install
6 and Windows).
11 - [Prerequisites](#prerequisites)
12 - [Notational Conventions](#notational-conventions)
13 - [Quick Installation Guide](#quick-installation-guide)
14 - [Building OpenSSL](#building-openssl)
15 - [Installing OpenSSL](#installing-openssl)
16 - [Configuration Options](#configuration-options)
17 - [API Level](#api-level)
18 - [Cross Compile Prefix](#cross-compile-prefix)
[all …]
|
| /third_party/skia/modules/canvaskit/ |
| D | README.md | 4 test dependencies. Recent installations of Node have npm as well.
9 compilation. Which version should you use? [`/infra/wasm-common/docker/emsdk-base/Dockerfile`][2]
10 shows the version we build and test with. We try to use as recent a version of emscripten as
14 [2]: https://github.com/google/skia/blob/main/infra/wasm-common/docker/emsdk-base/Dockerfile
16 Be sure to both install **and** activate the correct version. For example:
22 This document also assumes you have followed the instructions to download Skia and its deps
27 can fail with errors about SSL certificates. <https://github.com/emscripten-core/emsdk/pull/273>
29 See also <https://github.com/emscripten-core/emscripten/issues/9036#issuecomment-532092743>
32 # Compile and Run Local Example
35 # The following installs all npm dependencies and only needs to be when setting up
[all …]
|
| /third_party/skia/m133/third_party/externals/harfbuzz/ |
| D | TESTING.md | 1 ## Build and Test
4 meson build
5 ninja -Cbuild
6 meson test -Cbuild
12 meson test -Cbuild --gdb testname
15 ## Build and Run
18 Values defined in `hb-debug.hh`.
21 CPPFLAGS='-DHB_DEBUG_SUBSET=100' meson setup build --reconfigure
22 meson test -C build
28 meson setup build -Db_sanitize=address --reconfigure
[all …]
|
| /third_party/pcre2/pcre2/doc/html/ |
| D | NON-AUTOTOOLS-BUILD.txt | 2 --------------------------------------
15 Building PCRE2 on native z/OS and z/VM
22 C, and so should compile successfully on any system that has a Standard C
23 compiler and library.
26 configure/make (autotools) build system, as found in many Unix-like
31 environments, though it can also be run in Unix-like environments. See the
34 Versions of src/config.h and src/pcre2.h are distributed in the PCRE2 tarballs
35 under the names src/config.h.generic and src/pcre2.h.generic. These are
36 provided for those who build PCRE2 without using "configure" or CMake. If you
43 code unit width: 8, 16, or 32 bits. You can build any combination of them. The
[all …]
|
12345678910>>...45