Searched +full:cmake +full:- +full:build +full:- +full:and +full:- +full:test +full:- +full:check (Results 1 – 25 of 406) sorted by relevance
12345678910>>...17
| /external/clang/cmake/caches/ |
| D | README.txt | 1 CMake Caches
4 This directory contains CMake cache scripts that pre-populate the CMakeCache in
5 a build directory with commonly used settings.
7 You can use the caches files with the following CMake invocation:
9 cmake -G <build system>
10 -C <path to cache file>
11 [additional CMake options (i.e. -DCMAKE_INSTALL_PREFIX=<install path>)]
18 Apple-stage1
19 ------------
21 The Apple stage1 cache configures a two stage build similar to how Apple builds
[all …]
|
| /external/curl/ |
| D | Makefile.am | 14 # You may opt to use, copy, modify, merge, publish, distribute and/or sell
15 # copies of the Software, and permit persons to whom the Software is
21 # SPDX-License-Identifier: curl
27 ACLOCAL_AMFLAGS = -I m4
30 CMake/cmake_uninstall.cmake.in \
31 CMake/CMakeConfigurableFile.in \
32 CMake/curl-config.cmake.in \
33 CMake/CurlSymbolHiding.cmake \
34 CMake/CurlTests.c \
35 CMake/FindBearSSL.cmake \
[all …]
|
| /external/cronet/third_party/libc++/src/utils/ci/ |
| D | run-buildbot | 2 #===----------------------------------------------------------------------===##
6 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
8 #===----------------------------------------------------------------------===##
10 set -ex
11 set -o pipefail
23 [-h|--help] Display this help and exit.
25 --llvm-root <DIR> Path to the root of the LLVM monorepo. By default, we try
28 --build-dir <DIR> The directory to use for building the library. By default,
29 this is '<llvm-root>/build/<builder>'.
31 --osx-roots <DIR> Path to pre-downloaded macOS dylibs. By default, we download
[all …]
|
| /external/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 …]
|
| /external/openthread/third_party/mbedtls/repo/ |
| 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 …]
|
| /external/llvm/docs/ |
| D | AdvancedBuilds.rst | 2 Advanced Build Configurations
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
16 :doc:`CMake` pages. This page is intended for users doing more complex builds.
18 Many of the examples below are written assuming specific CMake Generators.
19 Unless otherwise explicitly called out these commands should work with any CMake
25 The Clang CMake build system supports bootstrap (aka multi-stage) builds. At a
26 high level a multi-stage build is a chain of builds that pass data from one
27 stage into the next. The most common and simple version of this is a traditional
28 bootstrap build.
[all …]
|
| /external/parameter-framework/upstream/ |
| D | appveyor.yml | 1 version: 3.0.0-{build}
9 # Disable popups as they hang the build as there is nobody to click on the OK button...
10 # Hanging the build is a lot less user friendly than reporting a build failure.
13 # See: https://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx
14 - reg add "HKLM\SYSTEM\CurrentControlSet\Control\Windows" /f /v ErrorMode /d 2
17 # | Windows can check online for a solution to the problem|
18 # | - Check online for a solution and close the program |
19 # | - Close the program |
20 # See: https://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx
21 - reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting" /f /v DontShowUI /d 1
[all …]
|
| /external/protobuf/cmake/ |
| D | README.md | 1 This directory contains *CMake* files that can be used to build protobuf
2 with *MSVC* on *Windows*. You can build the project from *Command Prompt*
3 and using an *Visual Studio* IDE.
5 You need to have [CMake](http://www.cmake.org), [Visual Studio](https://www.visualstudio.com)
6 and optionally [Git](http://git-scm.com) installed on your computer before proceeding.
31 If *cmake* command is not available from *Command Prompt*, add it to system *PATH* variable:
33 C:\Path\to>set PATH=%PATH%;C:\Program Files (x86)\CMake\bin
39 Optionally, you will want to download [ninja](https://ninja-build.org/) and add it to your *PATH* v…
52 For example: if you only need C++, download `protobuf-cpp-[VERSION].tar.gz`; if
53 you need C++ and Java, download `protobuf-java-[VERSION].tar.gz` (every package
[all …]
|
| /external/cronet/third_party/protobuf/cmake/ |
| D | README.md | 1 This directory contains *CMake* files that can be used to build protobuf
2 with *MSVC* on *Windows*. You can build the project from *Command Prompt*
3 and using an *Visual Studio* IDE.
5 You need to have [CMake](http://www.cmake.org), [Visual Studio](https://www.visualstudio.com)
6 and optionally [Git](http://git-scm.com) installed on your computer before proceeding.
31 If *cmake* command is not available from *Command Prompt*, add it to system *PATH* variable:
33 C:\Path\to>set PATH=%PATH%;C:\Program Files (x86)\CMake\bin
39 Optionally, you will want to download [ninja](https://ninja-build.org/) and add it to your *PATH* v…
52 For example: if you only need C++, download `protobuf-cpp-[VERSION].tar.gz`; if
53 you need C++ and Java, download `protobuf-java-[VERSION].tar.gz` (every package
[all …]
|
| /external/clang/docs/ |
| D | HowToSetupToolingForLLVM.rst | 6 and semantic information about a program. This term also relates to a set
7 of specific tools using this infrastructure (e.g. ``clang-check``). This
8 document provides information on how to set up and use Clang Tooling for
14 Clang Tooling needs a compilation database to figure out specific build
16 from the ``compilation_commands.json`` file, generated by CMake. When
17 invoking clang tools, you can either specify a path to a build directory
18 using a command line parameter ``-p`` or let Clang Tooling find this
20 build using CMake to use clang tools.
22 Setup Clang Tooling Using CMake and Make
25 If you intend to use make to build LLVM, you should have CMake 2.8.6 or
[all …]
|
| /external/oboe/tests/ |
| D | run_tests.sh | 9 # http://www.apache.org/licenses/LICENSE-2.0
14 # See the License for the specific language governing permissions and
18 # Script to build and run the Oboe tests on an attached Android device or emulator
21 # - CMake on PATH. This is usually found in $ANDROID_HOME/cmake/<version>/bin.
22 # - ANDROID_NDK environment variable is set to your Android NDK location
24 # - Android device or emulator attached and accessible via adb
27 # - Run this script
28 # - Check the test results on your target device
31 # - Builds a test binary for the target architecture
32 # - Copies the test binary into the UnitTestRunner app
[all …]
|
| /external/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
36 # * CMake
37 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
39 # * arm-gcc and mingw-gcc
[all …]
|
| /external/libevent/ |
| D | ChangeLog | 1 Changes in version 2.1.12-stable (05 Jul 2020)
8 it recommends itself better then travis/appveyor (and had been removed from
14 patches that touches only tests and similar):
18 o Merge branch 'event_rpcgen.py-cleanup' (f0ded5f3, 48e04887 Enji Cooper)
21 test:
23 o Merge branch 'osx-clock' (e85afbe3 Azat Khuzhin)
24 …o test-ratelim: calculate timers bias (for slow CPUs) to avoid false-positive (8ad26d0b Azat Khuzh…
28 o http: fix undefined-shift in EVUTIL_IS*_ helpers (6b8d02a7 Azat Khuzhin)
29 …o Check error code of evhttp_add_header_internal() in evhttp_parse_query_impl() (97e28f09 Azat Khu…
30 o http: fix EVHTTP_CON_AUTOFREE in case of timeout (and some else) (1be25938 Azat Khuzhin)
[all …]
|
| /external/cronet/third_party/google_benchmark/src/ |
| 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/goo…
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)
50 [Building and installing Python bindings](docs/python_bindings.md)
54 The library can be used with C++03. However, it requires C++11 to build,
55 including compiler and standard library support.
[all …]
|
| /external/google-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 …]
|
| /external/deqp-deps/SPIRV-Tools/kokoro/scripts/linux/ |
| D | build-docker.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0
13 # See the License for the specific language governing permissions and
16 # Linux Build Script.
19 set -e
21 set -x
24 # have changed between the clone environment, and the docker container.
26 git config --global --add safe.directory $ROOT_DIR
31 using clang-10.0.0
33 using gcc-9
40 if [[ -d "$dir" ]]; then
[all …]
|
| /external/swiftshader/third_party/SPIRV-Tools/kokoro/scripts/linux/ |
| D | build-docker.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0
13 # See the License for the specific language governing permissions and
16 # Linux Build Script.
19 set -e
21 set -x
24 # have changed between the clone environment, and the docker container.
26 git config --global --add safe.directory $ROOT_DIR
31 using clang-10.0.0
33 using gcc-9
40 if [[ -d "$dir" ]]; then
[all …]
|
| /external/angle/third_party/spirv-tools/src/kokoro/scripts/linux/ |
| D | build-docker.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0
13 # See the License for the specific language governing permissions and
16 # Linux Build Script.
19 set -e
21 set -x
24 # have changed between the clone environment, and the docker container.
26 git config --global --add safe.directory $ROOT_DIR
31 using clang-10.0.0
33 using gcc-9
40 if [[ -d "$dir" ]]; then
[all …]
|
| /external/rust/crates/libz-sys/src/zlib-ng/ |
| D | CMakeLists.txt | 7 message(STATUS "Using CMake version ${CMAKE_VERSION}")
15 …set(CMAKE_C_STANDARD 11) # The C standard whose features are requested to build this targ…
28 # Parse the full version number from zlib.h and include in ZLIB_FULL_VERSION
30 string(REGEX REPLACE ".*#define[ \t]+ZLIB_VERSION[ \t]+\"([0-9]+.[0-9]+.[0-9]+).*\".*"
32 string(REGEX REPLACE ".*#define[ \t]+ZLIBNG_VERSION[ \t]+\"([-0-9A-Za-z.]+)\".*"
49 include(cmake/detect-arch.cmake)
50 include(cmake/detect-install-dirs.cmake)
51 include(cmake/detect-coverage.cmake)
52 include(cmake/detect-intrinsics.cmake)
53 include(cmake/detect-sanitizer.cmake)
[all …]
|
| /external/cronet/third_party/libc++/src/docs/ |
| D | BuildingLibcxx.rst | 16 libc++ :ref:`here <using-libcxx>`.
21 non-functional. Use the CMake option ``CMAKE_INSTALL_PREFIX`` to select a safe
25 The default build
28 The default way of building libc++, libc++abi and libunwind is to root the CMake
30 umbrella, they are different in nature from other build tools, so it makes sense
31 to treat them as a separate set of entities. The default build can be achieved
32 with the following CMake invocation:
34 .. code-block:: bash
36 $ git clone https://github.com/llvm/llvm-project.git
37 $ cd llvm-project
[all …]
|
| /external/openthread/third_party/mbedtls/repo/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
36 # * CMake
37 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
39 # * arm-gcc and mingw-gcc
[all …]
|
| /external/libogg/ |
| D | README.md | 3 [](https://travis-ci.org/xi…
4 [](https://mf4.xiph.org/…
5 [ and later, the easiest way to get this library is to install
16 Xcode 4.2 or later. However if you want to install tip-of-trunk from here
19 The basic steps needed to build libc++ are:
23 * ``cd where-you-want-llvm-to-live``
24 * ``svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm``
28 * ``cd where-you-want-llvm-to-live``
30 * ``svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx``
34 * ``cd where-you-want-llvm-to-live``
36 * ``svn co http://llvm.org/svn/llvm-project/libcxxabi/trunk libcxxabi``
38 #. Configure and build libc++ with libc++abi:
[all …]
|
| /external/flac/ |
| D | README.md | 1 <!---
2 /* FLAC - Free Lossless Audio Codec
3 * Copyright (C) 2001-2009 Josh Coalson
4 * Copyright (C) 2011-2023 Xiph.Org Foundation
8 * are distributed under Xiph.Org's BSD-like license (see the file
9 * COPYING.Xiph in this distribution). All other programs, libraries, and
10 * plugins are distributed under the LGPL or GPL (see COPYING.LGPL and
20 --->
28 The files read and produced by this software are called FLAC files. As
30 can be read from and written to by other software as well, this software
[all …]
|
| /external/openthread/.github/workflows/ |
| D | build.yml | 5 # Redistribution and use in source and binary forms, with or without
8 # notice, this list of conditions and the following disclaimer.
10 # notice, this list of conditions and the following disclaimer in the
11 # documentation and/or other materials provided with the distribution.
16 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
17 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
29 name: Build
33 branches-ignore:
[all …]
|
12345678910>>...17