Searched +full:build +full:- +full:and +full:- +full:test (Results 1 – 25 of 1169) sorted by relevance
12345678910>>...47
| /third_party/boost/libs/math/test/ |
| D | Jamfile.v2 | 1 # Copyright Daryle Walker, Hubert Holin, John Maddock 2006 - 2007 2 # copyright Paul A. Bristow 2006 - 2010 6 # \math_toolkit\libs\math\test\jamfile.v2 8 # and build math examples. 17 local ntl-path = [ modules.peek : NTL_PATH ] ; 22 # PCH support is broken when --remove-test-targets is specified on the command 25 local remove-test-targets = [ MATCH (--remove-test-targets) : [ modules.peek : ARGV ] ] ; 27 if $(remove-test-targets) 39 <toolset>intel-win:<cxxflags>-nologo 40 <toolset>intel-win:<linkflags>-nologo [all …]
|
| /third_party/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 …]
|
| /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… 8 [](https://travis-ci.org/g… 32 To get started, see [Requirements](#requirements) and 33 [Installation](#installation). See [Usage](#usage) for a full example and the 36 It may also help to read the [Google Test documentation](https://github.com/google/googletest/blob/… 41 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss) 52 The library can be used with C++03. However, it requires C++11 to build, 53 including compiler and standard library support. 55 The following minimum versions are required to build the library: [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/libuv/ |
| 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/). 47 The documentation is licensed under the CC BY 4.0 license. Check the [LICENSE-docs file](LICENSE-do… 58 Located in the docs/ subdirectory. It uses the [Sphinx](http://sphinx-doc.org/) [all …]
|
| D | ChangeLog | 7 * macos: don't use thread-unsafe strtok() (Ben Noordhuis) 30 * test: test with maximum recvmmsg buffer (Ondřej Surý) 40 * test: fix flaky uv_fs_lutime test (Momtchil Momtchev) 42 * build: fix cmake install locations (Jameson Nash) 46 * build: rename CFLAGS to AM_CFLAGS (Jameson Nash) 48 * doc/guide: update content and sample code (woclass) 52 * test: remove flaky test ipc_closed_handle (Ben Noordhuis) 58 * build: export uv_a for cmake (WenTao Ou) 60 * loop: add pending work to loop-alive check (Jameson Nash) 68 * bench: add `uv_queue_work` ping-pong measurement (Momtchil Momtchev) [all …]
|
| /third_party/libpsl/ |
| D | README.MSVC.md | 15 complete the build successfully. 18 libraries, headers and DLLs, to build libpsl, unless both 19 DISABLE_BUILTIN=1 and DISABLE_RUNTIME=1 are passed into the NMake 22 You can also buid libpsl with libiconv and gettext support, please 27 go to $(srcroot)\msvc, and issue the following command: 31 A 'test' target is provided to build the test programs, while a 32 'clean' target is provided to remove all the compiled and generated 33 files for the build. An 'install' target is provided to copy the 34 build PSL DLL, .lib and executables, as well as the related PDB files 35 and libpsl header, into appropriate locations under PREFIX (please see [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. 12 ------------------------ 13 - [Test History](#test-history) 14 - [Introduction](#introduction) 15 - [Test Environment Requirements](#test-environment-requirements) 16 - [Configuring and Building the Tests](#configuring-and-building-the-tests) 17 - [Configuration](#configuration) 18 - [Building the Tests](#building-the-tests) [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://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 …]
|
| /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/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/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/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/musl/ndk-test/ |
| D | README.en.md | 1 # Compile the test case 3 - [Introduction] 4 - [Directory] 5 - [Constraints and Limitations] 6 - [illustrate] 7 - [Description of related issues] 13 According to the needs of customers, compile and generate corresponding executable programs and lib… 17 3. Execute the compiled task by running cmake --build . 25 ├── ndk-test 26 │ ├── CMakeLists.txt # Starting point for ndk-test build via cmake [all …]
|
| /third_party/boost/libs/test/doc/closing_chapters/ |
| D | faq.qbk | 2 / Copyright (c) 2003 Boost.Test contributors 10 [h3 Where the latest version of the Boost Test Library is located?] 11 The latest version of Boost Test Library is available online at [@http://www.boost.org/libs/test]. 14 You can send a bug report to the boost users' mailing list and/or fill a ticket here [@https://svn.… 18 You can send a request to the boost developers' mailing list and/or and/or fill a ticket here [@htt… 21 [h3 How to create test case using the Unit Test Framework?] 22 To create a test case, use the macro 26 For more details see the Unit Test Framework __BOOST_AUTO_TEST_CASE__ documentation. 28 [h3 How to create test suite using the Unit Test Framework?] 29 To create a test suite use the macro [all …]
|
| /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 30 ['tools/bazel', 'query', '--noimplicit_deps', '--output', 'xml', query]) 96 # labels in form //test/core/util:port.cc 105 if dep.startswith('//:include/') and dep.endswith('.h'): 111 """Gets list of non-public headers from a bazel rule""" 114 if dep.startswith('//') and not dep.startswith( 115 '//:include/') and dep.endswith('.h'): 124 if dep.startswith('//') and (dep.endswith('.cc') or dep.endswith('.c') 149 """Sort library names to form correct build order. Use metadata from lib_dict""" [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 for running remote builds by following the ["Set credential… 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/manual.bazelrc test --config=opt //test/... 33 bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=asan //test/... 40 bazel --bazelrc=tools/remote_build/windows.bazelrc test --config=windows_opt //test/... [all …]
|
| /third_party/flutter/flutter/dev/devicelab/ |
| D | README.md | 4 Android and iOS devices. 6 This package contains the code for test framework and the tests. More generally 10 Build results are available at https://flutter-dashboard.appspot.com. 14 ## The build page 16 The build page is accessible at https://flutter-dashboard.appspot.com/build.html. 17 This page reports the health of build servers, called _agents_, and the statuses 18 of build tasks. 22 A green agent is considered healthy and ready to receive new tasks to build. A 23 red agent is broken and does not receive new tasks. 25 In the example below, the dashboard shows that the `linux2` agent is broken and [all …]
|
| /third_party/boost/libs/uuid/test/ |
| D | Jamfile.v2 | 2 # Copyright 2017 - 2018 James E. King III 9 project libs/uuid/test 13 # near-impossible with the platform selection logic in the random_provider 14 <target-os>windows:<define>BOOST_UUID_FORCE_AUTO_LINK 15 <target-os>windows,<toolset>gcc:<library>bcrypt 17 # boost::lexical_cast needs this for a warning-free build (CHAR_MAX) 18 <toolset>clang:<cxxflags>-Wno-c99-extensions 20 # boost::random needs this setting for a warning free build: 33 # this rule enumerates through all the headers and ensures 36 # on any other headers to be included first - adapted from [all …]
|
| /third_party/boost/libs/signals2/doc/ |
| D | tests.xml | 1 <?xml version="1.0" encoding="utf-8"?> 2 <!DOCTYPE testsuite PUBLIC "-//Boost//DTD BoostBook XML V1.0//EN" 4 <!-- 5 Copyright Douglas Gregor 2001-2004 6 Copyright Frank Mori Hess 2007-2009 10 --> 11 <testsuite last-revision="$Date: 2007-06-12 14:01:23 -0400 (Tue, 12 Jun 2007) $"> 12 <run-test filename="connection_test.cpp"> 13 <lib>../../../libs/test/build/boost_test_exec_monitor</lib> 15 <para>Test functionality of <classname>boost::signals2::connection</classname> [all …]
|
| /third_party/boost/tools/build/notes/ |
| D | release_procedure.txt | 14 Make sure that "bjam --version" output is correct. Update version string if 15 needed. Update bjam version and the version check is necessary. 19 1. Make sure you don't have any local modification, and create SVN directory 21 https://svn.boost.org/svn/boost/branches/build/Milestone_X 25 https://svn.boost.org/svn/boost/trunk/tools/build 32 svn co https://svn.boost.org/svn/boost/branches/build/Milestone_X boost-build 34 3. Go to "boost-build/build/v2" directory. 36 4. Run "./roll.sh". This will create "boost-build.zip" and 37 "boost-build.tar.bz2" in parent directory, and also upload 40 5. Unpack "boost-build.tar.bz2", and build jam. [all …]
|
| /third_party/openssl/ |
| D | INSTALL | 2 -------------------- 6 and Windows). 14 * a development environment in the form of development libraries and C 19 issues and other details, please read one of these: 28 --------------------------------------- 46 - or - 48 - or - 71 Note that the notation assumes spaces around {, }, [, ], {{, }} and 73 specifications, which also use [ and ], but without spaces. 76 ----------- [all …]
|
| /third_party/boost/ |
| D | bootstrap.sh | 2 # Copyright 2019-2021 René Ferdinand Rivera Morell 9 # boostinspect:notab - Tabs are required for the Makefile. 14 BUILD="" 26 # support -n. Use the installed echo executable if there is one 27 # rather than builtin version to ensure -n is supported. 29 if test "x$ECHO" = x; then 42 -help | --help | -h) 45 -prefix=* | --prefix=*) 46 PREFIX=`expr "x$option" : "x-*prefix=\(.*\)"` 49 -exec-prefix=* | --exec-prefix=*) [all …]
|
| /third_party/boost/tools/build/ |
| D | CONTRIBUTING.adoc | 1 // Copyright 2019-2020 Rene Rivera 8 B2 is an open-source project. This means that we welcome and appreciate 9 all contributions -- be it ideas, bug reports, or patches. This document 10 contains guidelines which helps to assure that development goes on smoothly, and 13 The guidelines are not mandatory, and you can decide for yourself which one to 18 at boost-build@lists.boost.org. 24 https://github.com/boostorg/build/issues 28 boost-build@lists.boost.org 30 http://lists.boost.org/boost-build/ 32 == BUGS and PATCHES [all …]
|
| /third_party/node/ |
| D | BUILDING.md | 3 Depending on what platform or features you need, the build process may 5 test suite to confirm that the binary works as intended is a good next step. 7 If you can reproduce a test failure, search for it in the 13 * [Supported platforms](#supported-platforms) 16 * [Platform list](#platform-list) 17 * [Supported toolchains](#supported-toolchains) 18 * [Official binary platforms and toolchains](#official-binary-platforms-and-toolchains) 19 * [OpenSSL asm support](#openssl-asm-support) 20 * [Previous versions of this document](#previous-versions-of-this-document) 21 * [Building Node.js on supported platforms](#building-nodejs-on-supported-platforms) [all …]
|
12345678910>>...47