Searched +full:cmake +full:- (Results 1 – 25 of 1034) sorted by relevance
12345678910>>...42
| /external/llvm/docs/ |
| D | CMakePrimer.rst | 2 CMake Primer
10 anyone affiliated with the CMake project. This document may contain
18 The LLVM project and many of the core projects built on LLVM build using CMake.
19 This document aims to provide a brief overview of CMake for developers modifying
22 The official CMake language references is available in the cmake-language
23 manpage and `cmake-language online documentation
24 <https://cmake.org/cmake/help/v3.4/manual/cmake-language.7.html>`_.
29 CMake is a tool that reads script files in its own language that describe how a
30 software project builds. As CMake evaluates the scripts it constructs an
32 fully processed, if there are no errors, CMake will generate build files to
[all …]
|
| D | CMake.rst | 2 Building LLVM with CMake
11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
20 `Quick start`_ section. If you are a CMake novice, start with `Basic CMake usage`_
23 you already have experience with CMake, this is the recommended starting point.
25 This page is geared towards users of the LLVM CMake build. If you're looking for
26 information about modifying the LLVM CMake build system you may want to see the
27 :doc:`CMakePrimer` page. It has a basic overview of the CMake language.
34 We use here the command-line, non-interactive CMake interface.
36 #. `Download <http://www.cmake.org/cmake/resources/software.html>`_ and install
37 CMake. Version 3.4.3 is the minimum required.
[all …]
|
| D | AdvancedBuilds.rst | 11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
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
30 In a simple two-stage bootstrap build, we build clang using the system compiler,
31 then use that just-built clang to build clang again. In CMake this simplest form
35 .. code-block:: console
37 $ cmake -G Ninja -DCLANG_ENABLE_BOOTSTRAP=On <path to source>
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | CMakePrimer.rst | 2 CMake Primer
10 anyone affiliated with the CMake project. This document may contain
18 The LLVM project and many of the core projects built on LLVM build using CMake.
19 This document aims to provide a brief overview of CMake for developers modifying
22 The official CMake language references is available in the cmake-language
23 manpage and `cmake-language online documentation
24 <https://cmake.org/cmake/help/v3.4/manual/cmake-language.7.html>`_.
29 CMake is a tool that reads script files in its own language that describe how a
30 software project builds. As CMake evaluates the scripts it constructs an
32 fully processed, if there are no errors, CMake will generate build files to
[all …]
|
| D | CMake.rst | 2 Building LLVM with CMake
11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
20 `Quick start`_ section. If you are a CMake novice, start with `Basic CMake usage`_
23 you already have experience with CMake, this is the recommended starting point.
25 This page is geared towards users of the LLVM CMake build. If you're looking for
26 information about modifying the LLVM CMake build system you may want to see the
27 :doc:`CMakePrimer` page. It has a basic overview of the CMake language.
34 We use here the command-line, non-interactive CMake interface.
36 #. `Download <http://www.cmake.org/cmake/resources/software.html>`_ and install
37 CMake. Version 3.4.3 is the minimum required.
[all …]
|
| D | AdvancedBuilds.rst | 11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
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
30 In a simple two-stage bootstrap build, we build clang using the system compiler,
31 then use that just-built clang to build clang again. In CMake this simplest form
35 .. code-block:: console
37 $ cmake -G Ninja -DCLANG_ENABLE_BOOTSTRAP=On <path to source>
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/cmake/modules/ |
| D | CMakeLists.txt | 1 set(LLVM_INSTALL_PACKAGE_DIR lib${LLVM_LIBDIR_SUFFIX}/cmake/llvm)
4 # First for users who use an installed LLVM, create the LLVMExports.cmake file.
5 set(LLVM_EXPORTS_FILE ${llvm_cmake_builddir}/LLVMExports.cmake)
11 set(LLVM_BUILDTREEONLY_EXPORTS_FILE ${llvm_cmake_builddir}/LLVMBuildTreeOnlyTargets.cmake)
23 # CMake requires that all targets expressed as dependencies exist, so we can't
25 # projects building out of tree will have CMake errors. This only gets hit when
32 # Generate LLVMConfig.cmake for the build tree.
57 # one from the build tree. This is due to our cmake files being split between
60 # tree, both the generated LLVMExports.cmake file and the rest of the cmake
61 # source files are put in the same cmake directory.
[all …]
|
| /external/catch2/docs/ |
| D | cmake-integration.md | 2 # CMake integration
5 [CMake target](#cmake-target)<br>
6 [Automatic test registration](#automatic-test-registration)<br>
7 [CMake project options](#cmake-project-options)<br>
8 [Installing Catch2 from git repository](#installing-catch2-from-git-repository)<br>
10 Because we use CMake to build Catch2, we also provide a couple of
13 1) Catch2 exports a (namespaced) CMake target
14 2) Catch2's repository contains CMake scripts for automatic registration
17 ## CMake target
19 Catch2's CMake build exports an interface target `Catch2::Catch2`. Linking
[all …]
|
| /external/curl/docs/ |
| D | INSTALL.cmake | 7 How To Compile with CMake
9 Building with CMake
12 from source code using the CMake build tool. To build with CMake, you will
13 of course have to first install CMake. The minimum required version of
14 CMake is specified in the file CMakeLists.txt found in the top of the curl
15 source tree. Once the correct version of CMake is installed you can follow
18 CMake builds can be configured either from the command line, or from one
19 of CMake's GUI's.
21 Current flaws in the curl CMake build
24 Missing features in the cmake build:
[all …]
|
| /external/boringssl/src/ |
| D | BUILDING.md | 5 The standalone CMake build is primarily intended for developers. If embedding
6 BoringSSL into another project with a pre-existing build system, see
13 * [CMake](https://cmake.org/download/) 2.8.12 or later is required. Note we
14 will begin requiring CMake 3.0 in 2019.
22 If Perl is not found by CMake, it may be configured explicitly by setting
25 * Building with [Ninja](https://ninja-build.org/) instead of Make is
26 recommended, because it makes builds faster. On Windows, CMake's Visual
28 recent versions of CMake for assembly support.
31 by CMake, it may be configured explicitly by setting
36 Recent versions of GCC (4.8+) and Clang should work on non-Windows
[all …]
|
| /external/libjpeg-turbo/ |
| D | BUILDING.md | 1 Building libjpeg-turbo
6 ------------------
11 - [CMake](http://www.cmake.org) v2.8.12 or later
13 - [NASM](http://www.nasm.us) or [YASM](http://yasm.tortall.net)
14 (if building x86 or x86-64 SIMD extensions)
16 * If using NASM, 2.10 or later (except 2.11.08) is required for an x86-64 Mac
17 build (2.11.08 does not work properly with libjpeg-turbo's x86-64 SIMD code
21 - NOTE: Currently, if it is desirable to hide the SIMD function symbols in
23 libjpeg-turbo, then YASM must be used when building libjpeg-turbo.
34 ARCH=`uname -m`
[all …]
|
| /external/libaom/libaom/ |
| D | README.md | 4 1. [Building the lib and applications](#building-the-library-and-applications)
5 - [Prerequisites](#prerequisites)
6 - [Get the code](#get-the-code)
7 - [Basics](#basic-build)
8 - [Configuration options](#configuration-options)
9 - [Dylib builds](#dylib-builds)
10 - [Debugging](#debugging)
11 - [Cross compiling](#cross-compiling)
12 - [Sanitizer support](#sanitizers)
13 - [MSVC builds](#microsoft-visual-studio-builds)
[all …]
|
| /external/llvm/cmake/modules/ |
| D | CMakeLists.txt | 1 set(LLVM_INSTALL_PACKAGE_DIR lib${LLVM_LIBDIR_SUFFIX}/cmake/llvm)
6 FILE ${llvm_cmake_builddir}/LLVMExports.cmake)
16 # Generate LLVMConfig.cmake for the build tree.
34 set(LLVM_CONFIG_EXPORTS_FILE "${llvm_cmake_builddir}/LLVMExports.cmake")
36 LLVMConfig.cmake.in
37 ${llvm_cmake_builddir}/LLVMConfig.cmake
45 FILES_MATCHING PATTERN *.cmake
50 # Generate LLVMConfig.cmake for the install tree.
52 # Compute the installation prefix from this LLVMConfig.cmake file location.
66 set(LLVM_CONFIG_EXPORTS_FILE "\${LLVM_CMAKE_DIR}/LLVMExports.cmake")
[all …]
|
| /external/protobuf/cmake/ |
| D | README.md | 1 This directory contains *CMake* files that can be used to build protobuf
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
48 C:\Path\to> git clone -b [release_tag] https://github.com/google/protobuf.git
50 Where *[release_tag]* is a git tag like *v3.0.0-beta-1* or a branch name like *master*
58 Protobuf unit-tests require gmock to build. If you download protobuf source code
61 download it manually or skip building protobuf unit-tests.
65 C:\Path\to\protobuf>git clone -b release-1.7.0 https://github.com/google/googlemock.git gmock
[all …]
|
| /external/flatbuffers/ |
| D | conanfile.py | 2 # -*- coding: utf-8 -*-
8 from conans import ConanFile, CMake, tools
13 license = "Apache-2.0"
17 topics = ("conan", "flatbuffers", "serialization", "rpc", "json-parser")
22 generators = "cmake"
24 …exports_sources = ["CMake/*", "include/*", "src/*", "grpc/*", "CMakeLists.txt", "conan/CMakeLists.…
27 """Wrap the original CMake file to call conan_basic_setup
39 """Create CMake instance and execute configure step
41 cmake = CMake(self)
42 cmake.definitions["FLATBUFFERS_BUILD_TESTS"] = False
[all …]
|
| /external/vulkan-validation-layers/ |
| D | BUILD.md | 8 1. [Contributing](#contributing-to-the-repository)
9 1. [Repository Content](#repository-content)
10 1. [Repository Set-Up](#repository-set-up)
11 1. [Windows Build](#building-on-windows)
12 1. [Linux Build](#building-on-linux)
13 1. [Android Build](#building-on-android)
14 1. [MacOS build](#building-on-macos)
33 - *install_dir*`/lib` : The Vulkan validation layer libraries
34 - *install_dir*`/share/vulkan/explicit_layer.d` : The Vulkan validation layer
40 ## Repository Set-Up
[all …]
|
| /external/grpc-grpc/test/distrib/cpp/ |
| D | run_distrib_test_cmake.bat | 7 @rem http://www.apache.org/licenses/LICENSE-2.0
18 @rem TODO(jtattermusch): Kokoro has pre-installed protoc.exe in C:\Program Files\ProtoC and that di…
19 …TH. To avoid picking up the older version protoc.exe, we change the path to something non-existent.
25 @rem Download OpenSSL-Win32 originally installed from https://slproweb.com/products/Win32OpenSSL.ht…
26 …hell -Command "(New-Object Net.WebClient).DownloadFile('https://storage.googleapis.com/grpc-testin…
27 powershell -Command "Add-Type -Assembly 'System.IO.Compression.FileSystem'; [System.IO.Compression.…
30 set OPENSSL_DIR=%cd:\=/%/OpenSSL-Win32
33 mkdir cmake
34 cd cmake
35 cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_DIR% ..
[all …]
|
| D | run_distrib_test_cmake.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0
16 set -ex
20 echo "deb http://ftp.debian.org/debian jessie-backports main" | tee /etc/apt/sources.list.d/jessie-…
21 apt-get update
22 apt-get install -t jessie-backports -y libssl-dev
24 # Install c-ares
27 git checkout cares-1_13_0
28 mkdir -p cmake/build
29 cd cmake/build
30 cmake -DCMAKE_BUILD_TYPE=Release ../..
[all …]
|
| /external/freetype/ |
| D | CMakeLists.txt | 3 # Copyright 2013-2018 by
16 # call cmake to configure the build with default parameters as a static
19 # cmake -E make_directory build
20 # cmake -E chdir build cmake ..
24 # cmake -E chdir build cmake -D BUILD_SHARED_LIBS:BOOL=true ..
28 # cmake -E chdir build cmake -G Xcode -D BUILD_FRAMEWORK:BOOL=true ..
32 # cmake -E chdir build cmake -G Xcode -D IOS_PLATFORM=OS ..
36 # cmake -E chdir build cmake -G Xcode -D IOS_PLATFORM=SIMULATOR ..
40 # cmake -E chdir build cmake -G Xcode -D IOS_PLATFORM=SIMULATOR64 ..
44 # cmake --build build
[all …]
|
| /external/capstone/ |
| D | COMPILE_CMAKE.TXT | 1 This documentation explains how to compile Capstone with CMake, focus on
8 *-*-*-*-*-*
10 This documentation requires CMake & Windows SDK or MS Visual Studio installed on
13 Get CMake for free from http://www.cmake.org.
20 SystemZ, X86 & XCore), if you just need several selected archs, run "cmake"
23 - CAPSTONE_ARM_SUPPORT: support ARM. Run cmake with -DCAPSTONE_ARM_SUPPORT=0 to remove ARM.
24 …- CAPSTONE_ARM64_SUPPORT: support ARM64. Run cmake with -DCAPSTONE_ARM64_SUPPORT=0 to remove ARM64.
25 - CAPSTONE_MIPS_SUPPORT: support Mips. Run cmake with -DCAPSTONE_MIPS_SUPPORT=0 to remove Mips.
26 - CAPSTONE_PPC_SUPPORT: support PPC. Run cmake with -DCAPSTONE_PPC_SUPPORT=0 to remove PPC.
27 …- CAPSTONE_SPARC_SUPPORT: support Sparc. Run cmake with -DCAPSTONE_SPARC_SUPPORT=0 to remove Sparc.
[all …]
|
| /external/vulkan-headers/ |
| D | BUILD.md | 7 1. [Contributing](#contributing-to-the-repository)
8 1. [Repository Content](#repository-content)
9 1. [Repository Set-up](#repository-set-up)
10 1. [Windows Build](#building-on-windows)
11 1. [Linux Build](#building-on-linux)
12 1. [MacOS Build](#building-on-macos)
17 API specification [repository](https://github.com/KhronosGroup/Vulkan-Docs).
26 However, this repository contains CMake build configuration files to "install"
30 If you are building other Vulkan-related repositories such as
31 [Vulkan-Loader](https://github.com/KhronosGroup/Vulkan-Loader),
[all …]
|
| /external/freetype/builds/cmake/ |
| D | testbuild.sh | 1 #!/bin/sh -e
3 # Copyright 2015-2018 by
12 # This script tests the CMake build. Simply run
14 # builds/cmake/testbuild.sh
18 # BUILD_SHARED_LIBS=1 builds/cmake/testbuild.sh
22 # - builds the main CMakeLists.txt
23 # - builds and runs a small test app in a separate build tree so
24 # the config-module is tested, too
28 # - The variable BUILD_SHARED_LIBS will be forwarded to the CMake project
37 tmpdir=/tmp/freetype-cmake-testbuild
[all …]
|
| /external/eigen/doc/ |
| D | TopicCMakeGuide.dox | 5 \page TopicCMakeGuide Using %Eigen in CMake Projects
7 %Eigen provides native CMake support which allows the library to be easily
8 used in CMake projects.
10 \note %CMake 3.0 (or later) is required to enable this functionality.
12 %Eigen exports a CMake target called `Eigen3::Eigen` which can be imported
13 using the `find_package` CMake command and used by calling
15 \code{.cmake}
28 $ cmake path-to-example-directory
30 CMake will produce project files that generate an executable called `example`
31 which requires at least version 3.3 of %Eigen. Here, `path-to-example-directory`
[all …]
|
| /external/tensorflow/tensorflow/contrib/cmake/ |
| D | README.md | 1 TensorFlow CMake build
4 CMAKE build is deprecated for TensorFlow. Please use `bazel` to build TF for all
8 This directory contains CMake files for building TensorFlow on Microsoft Windows
9 and Linux. [CMake](https://cmake.org) is a cross-platform tool that can generate
14 testing the build. We recommend using the standard Bazel-based build on
18 --------------
20 CMake can be used to build TensorFlow on all platforms. See the
22 for instructions on how to install a pre-built TensorFlow package on Windows and
32 ## Building with CMake
34 The CMake files in this directory can build the core TensorFlow runtime, an
[all …]
|
| /external/clang/cmake/caches/ |
| D | README.txt | 1 CMake Caches
4 This directory contains CMake cache scripts that pre-populate the CMakeCache in
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 ------------
25 The Apple-stage2 cache can be used directly to match the build settings Apple
29 ---
[all …]
|
12345678910>>...42