Searched +refs:cmake +refs:variables (Results 1 – 25 of 699) sorted by relevance
12345678910>>...28
/aosp_15_r20/external/pigweed/pw_build/ |
H A D | cmake.rst | 1 .. _module-pw_build-cmake: 19 This will install any required packages, generate cmake build files and invkoke ninja. 27 …cmake --fresh --debug-output -DCMAKE_MESSAGE_LOG_LEVEL=WARNING -S . -B ./out/cmake -G Ninja -DCMAK… 28 …19:37:10 INF [1/1] Run ==> ninja -C out/cmake pw_apps pw_run_tests.modules pw_run_tests.pw_bluetoo… 39 CMake convenience functions are defined in ``pw_build/pigweed.cmake``. 70 See ``pw_build/pigweed.cmake`` for the complete documentation of these 78 The CMake build uses CMake cache variables for configuring 79 :ref:`facades<docs-module-structure-facades>` and backends. Cache variables are 81 support multi-toolchain builds, so these variables have a single global value 85 ``<module_name>_BACKEND`` for each facade. Cache variables can be awkward to [all …]
|
/aosp_15_r20/prebuilts/cmake/linux-x86/share/cmake-3.22/Help/manual/ |
D | OPTIONS_HELP.txt | 36 The :manual:`cmake-commands(7)` manual entry for ``<cmd>`` is 48 Print cmake-commands manual and exit. 50 The :manual:`cmake-commands(7)` manual is printed in a 57 The :manual:`cmake-modules(7)` manual entry for ``<mod>`` is printed 69 Print cmake-modules manual and exit. 71 The :manual:`cmake-modules(7)` manual is printed in a human-readable 78 The :manual:`cmake-policies(7)` manual entry for ``<cmp>`` is 90 Print cmake-policies manual and exit. 92 The :manual:`cmake-policies(7)` manual is printed in a 99 The :manual:`cmake-properties(7)` manual entries for ``<prop>`` are [all …]
|
D | cmake-developer.7.rst | 1 .. cmake-manual-description: CMake Developer Reference 3 cmake-developer(7) 14 :manual:`cmake-language(7)` code, whether writing their own modules, 17 See https://cmake.org/get-involved/ to get involved in development of 26 A "find module" is a ``Find<PackageName>.cmake`` file to be loaded by the 31 provide any variables, macros and imported targets required to use the 35 The traditional approach is to use variables for everything, including 45 In either case (or even when providing both variables and imported 49 A FindFoo.cmake module will typically be loaded by the command:: 58 variables are set for the find module. Most of these are dealt with by [all …]
|
D | cmake-packages.7.rst | 1 .. cmake-manual-description: CMake Packages Reference 3 cmake-packages(7) 16 a set of variables corresponding to build-relevant information. 27 .. code-block:: cmake 37 .. code-block:: cmake 44 .. code-block:: cmake 54 .. code-block:: cmake 60 .. code-block:: cmake 66 .. code-block:: cmake 89 a CMake user to tell :manual:`cmake(1)` to search in a non-standard prefix for [all …]
|
D | cmake.1.rst | 1 .. cmake-manual-description: CMake Command-Line Reference 3 cmake(1) 12 cmake [<options>] <path-to-source> 13 cmake [<options>] <path-to-existing-build> 14 cmake [<options>] -S <path-to-source> -B <path-to-build> 17 cmake --build <dir> [<options>] [-- <build-tool-options>] 20 cmake --install <dir> [<options>] 23 cmake --open <dir> 26 cmake [{-D <var>=<value>}...] -P <cmake-script-file> 29 cmake -E <command> [<options>] [all …]
|
D | cmake-language.7.rst | 1 .. cmake-manual-description: CMake Language Reference 3 cmake-language(7) 14 named ``CMakeLists.txt`` or ending in a ``.cmake`` file name extension. 19 * `Scripts`_ (``<script>.cmake``), and 20 * `Modules`_ (``<module>.cmake``). 38 An individual ``<script>.cmake`` source file may be processed 39 in *script mode* by using the :manual:`cmake(1)` command-line tool 49 use the :command:`include` command to load a ``<module>.cmake`` 51 See the :manual:`cmake-modules(7)` manual page for documentation 131 .. code-block:: cmake [all …]
|
D | cmake-toolchains.7.rst | 1 .. cmake-manual-description: CMake Toolchains Reference 3 cmake-toolchains(7) 24 built-in variables, such as 31 .. code-block:: cmake 38 .. code-block:: cmake 45 .. code-block:: cmake 60 Several variables relate to the language components of a toolchain which are 66 The :variable:`CMAKE_<LANG>_FLAGS` variables and the configuration-specific 98 If :manual:`cmake(1)` is invoked with the command line parameter 105 variables inside a toolchain file is typically undesirable. The toolchain [all …]
|
/aosp_15_r20/prebuilts/cmake/linux-x86/share/cmake-3.22/Modules/ |
D | FindOpenSceneGraph.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details. 23 :module:`Findosg` and ``Find<etc>.cmake`` files into your 28 This module accepts the following variables (note mixed case) 38 OpenSceneGraph_MARK_AS_ADVANCED - Mark cache variables as advanced 43 The following environment variables are also respected for finding the 49 a :module:`FindosgVolume`.cmake` file) 62 This module defines the following output variables: 106 # Local variables of the form _osg_foo 107 # Input variables of the form OpenSceneGraph_FOO 108 # Output variables of the form OPENSCENEGRAPH_FOO [all …]
|
D | FindCups.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details. 21 Result variables 24 This module will set the following variables in your project: 35 Cache variables 38 The following cache variables may also be set: 49 include(${CMAKE_CURRENT_LIST_DIR}/CheckLibraryExists.cmake) 50 include(${CMAKE_CURRENT_LIST_DIR}/CMakePushCheckState.cmake) 78 include(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake)
|
D | FetchContent.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details. 33 .. code-block:: cmake 74 .. code-block:: cmake 85 # Set custom variables, policies, etc. 103 .. code-block:: cmake 135 .. code-block:: cmake 167 :variable:`CMAKE_NETRC` and :variable:`CMAKE_NETRC_FILE` variables now 169 they do for :command:`ExternalProject_Add`. Previously, these variables 176 .. code-block:: cmake 186 ``<lowercaseName>_BINARY_DIR`` variables in the same way as a call to [all …]
|
D | FindBZip2.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details. 21 This module defines the following variables: 35 Cache variables 38 The following cache variables may also be set: 54 include(${CMAKE_CURRENT_LIST_DIR}/SelectLibraryConfigurations.cmake) 65 include(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake) 72 include(${CMAKE_CURRENT_LIST_DIR}/CheckSymbolExists.cmake) 73 include(${CMAKE_CURRENT_LIST_DIR}/CMakePushCheckState.cmake)
|
D | FindPkgConfig.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details. 12 following variables will also be set: 32 for how these variables are initialized. 37 cmake_policy(SET CMP0054 NEW) # if() quoted variables not dereferenced 98 include(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake) 109 # Unsets the given variables 126 # Invokes pkgconfig, cleans up the result and sets variables 359 # from the CMAKE_PREFIX_PATH variables 421 # Unset variables 607 # exist. Now, go through them and set variables [all …]
|
/aosp_15_r20/prebuilts/cmake/linux-x86/share/cmake-3.22/Help/command/ |
D | set.rst | 5 See the :ref:`cmake-language(7) variables <CMake Language Variables>` 6 documentation for the scopes and interaction of normal variables 12 value to be set. Zero arguments will cause normal variables to be 13 unset. See the :command:`unset` command to unset variables explicitly. 18 .. code-block:: cmake 35 .. code-block:: cmake 47 Boolean ``ON/OFF`` value. :manual:`cmake-gui(1)` offers a checkbox. 50 Path to a file on disk. :manual:`cmake-gui(1)` offers a file dialog. 53 Path to a directory on disk. :manual:`cmake-gui(1)` offers a file dialog. 56 A line of text. :manual:`cmake-gui(1)` offers a text field or a [all …]
|
D | find_package.rst | 17 In this mode, CMake searches for a file called ``Find<PackageName>.cmake``, 25 The ``Find<PackageName>.cmake`` file is not typically provided by the 38 ``<lowercasePackageName>-config.cmake`` or ``<PackageName>Config.cmake``. 39 It will also look for ``<lowercasePackageName>-config-version.cmake`` or 40 ``<PackageName>ConfigVersion.cmake`` if version details were specified 77 .. code-block:: cmake 90 package-specific information may be provided through other variables and 152 .. code-block:: cmake 187 The command searches for a file called ``<PackageName>Config.cmake`` or 188 ``<lowercasePackageName>-config.cmake`` for each name specified. [all …]
|
D | foreach.rst | 6 .. code-block:: cmake 32 .. code-block:: cmake 39 .. code-block:: cmake 51 .. code-block:: cmake 56 separated list of list-valued variables. The ``foreach`` 66 .. code-block:: cmake 90 .. code-block:: cmake 97 separated list of list-valued variables. The ``foreach`` 99 iteration variables as follows: 102 ``loop_var_N`` variables to the current item from the [all …]
|
D | mark_as_advanced.rst | 4 Mark cmake cached variables as advanced. 6 .. code-block:: cmake 11 cached variables. 14 of the cmake GUIs unless the ``show advanced`` option is on. 18 then advanced variables are changed back to unadvanced. 20 then the variables are made advanced.
|
/aosp_15_r20/external/llvm/docs/ |
H A D | CMake.rst | 11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake 22 `Options and variables`_ section is a reference for customizing your build. If 36 #. `Download <http://www.cmake.org/cmake/resources/software.html>`_ and install 55 $ cmake path/to/llvm/source/root 59 for all build parameters. See the `Options and variables`_ section for 75 $ cmake --build . 77 The ``--build`` option tells ``cmake`` to invoke the underlying build 87 $ cmake --build . --target install 90 the ``--build`` option tells ``cmake`` to build the ``install`` target. 93 by invoking the ``cmake_install.cmake`` script generated in the [all …]
|
H A D | CMakePrimer.rst | 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>`_. 55 .. code-block:: cmake 65 .. code-block:: cmake 80 In CMake variables are "stringly" typed. All variables are represented as 91 .. code-block:: cmake 98 pattern in CMake to conditionally set variables knowing that it will be used in 104 .. code-block:: cmake 118 .. code-block:: cmake [all …]
|
/aosp_15_r20/prebuilts/cmake/linux-x86/share/cmake-3.22/Help/release/ |
D | 3.5.rst | 16 * The :manual:`cmake-gui(1)` gained options to control warnings about 19 * The :manual:`cmake-gui(1)` learned an option to set the toolset 21 existing ``-T`` option to :manual:`cmake(1)`. 23 * The :manual:`cmake-gui(1)` gained a Regular Expression Explorer which 30 * The ``-Wdev`` and ``-Wno-dev`` :manual:`cmake(1)` options now also enable 34 the new ``-Werror=dev`` and ``-Wno-error=dev`` :manual:`cmake(1)` options. 36 * The :manual:`cmake(1)` ``-E`` command-line tools ``copy``, 48 :manual:`generator expressions <cmake-generator-expressions(7)>` 55 ``-Werror=deprecated`` and ``-Wno-error=deprecated`` :manual:`cmake(1)` 59 ``-Wdeprecated`` and ``-Wno-deprecated`` :manual:`cmake(1)` options. [all …]
|
D | 3.18.rst | 22 * :manual:`cmake(1)` gained support for profiling of CMake scripts through 25 * :manual:`cmake(1)` gained a ``cat`` command line 47 ``ARCHIVE_EXTRACT`` subcommands to expose the :manual:`cmake(1)` ``-E tar`` 118 :manual:`generator expressions <cmake-generator-expressions(7)>`. 176 * gained the possibility to create per-artifact cache variables for 177 interactive editing in :manual:`cmake-gui(1)` and :manual:`ccmake(1)`. 185 * The :module:`FindRuby` module input and output variables were all renamed 187 Input variables of the old case will be honored if provided, and output 188 variables of the old case are always provided. 215 :manual:`generator expressions <cmake-generator-expressions(7)>` were added [all …]
|
D | 3.12.rst | 18 value (e.g. via the :manual:`cmake(1)` ``-T`` option) to specify a 24 * The :manual:`cmake(1)` :ref:`Build Tool Mode` (``cmake --build``) gained 71 parameter which has the effect of setting variables like 96 * ``CMAKE_PROJECT_VERSION*`` variables have been introduced: 108 * ``CMAKE_VS_SDK_*_DIRECTORIES`` variables were defined to tell 111 variables are: 144 :manual:`generator expressions <cmake-generator-expressions(7)>`. 205 :manual:`generator expression <cmake-generator-expressions(7)>` 210 :manual:`generator expression <cmake-generator-expressions(7)>` 214 :manual:`generator expression <cmake-generator-expressions(7)>` [all …]
|
/aosp_15_r20/external/libjpeg-turbo/ |
H A D | BUILDING.md | 11 - [CMake](http://www.cmake.org) v2.8.12 or later 58 `PATH` environment variables. This is generally accomplished by 126 cmake -G"Unix Makefiles" [additional CMake flags] {source_directory} 169 cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release [additional CMake flags] {source_directory} 202 (run `cmake` with no arguments for a list of available generators.) For 206 cmake -G"Visual Studio 10" [additional CMake flags] {source_directory} 248 cmake -G"MSYS Makefiles" [additional CMake flags] {source_directory} 323 CMake variables can also be used to specify alternate commands or locations for 338 Use export/setenv to set the following environment variables before running 347 Use export/setenv to set the following environment variables before running [all …]
|
/aosp_15_r20/external/gflags/ |
H A D | CMakeLists.txt | 3 ## This CMakeLists.txt defines some gflags specific configuration variables 4 ## using the "gflags_define" utility macro. The default values of these variables 6 ## the cmake command or in a super-project which includes the gflags source 7 ## tree by setting the GFLAGS_<varname> CMake variables before adding the 10 ## these configuration variables are added to the CMake cache so they can be 85 include ("${CMAKE_CURRENT_SOURCE_DIR}/cmake/utils.cmake") 102 # - CheckTypeSize.cmake (fixed in CMake 3.1, cf. https://cmake.org/Bug/view.php?id=14056) 103 # - FindThreads.cmake (fixed in CMake 3.4, cf. https://cmake.org/Bug/view.php?id=14905) 128 # tree of a project that uses it, no variables should be added to the CMake cache; 138 # prefix for package variables in CMake configuration file [all …]
|
/aosp_15_r20/external/tensorflow/tensorflow/compiler/xla/mlir_hlo/cmake/modules/ |
H A D | CMakeLists.txt | 2 # link against them. LLVM calls its version of this file LLVMExports.cmake, but 3 # the usual CMake convention is ${Project}Targets.cmake. 5 # (llvm-project:mlir/cmake/modules). 9 set(MHLO_INSTALL_PACKAGE_DIR lib${LLVM_LIBDIR_SUFFIX}/cmake/mlir-hlo) 12 # Keep this in sync with llvm/cmake/CMakeLists.txt! 13 set(LLVM_INSTALL_PACKAGE_DIR lib${LLVM_LIBDIR_SUFFIX}/cmake/llvm) 16 # Since we just use MLIR's cmake functions (add_mlir_library, etc.), 19 export(TARGETS ${MLIR_EXPORTS} FILE ${mhlo_cmake_builddir}/MHLOTargets.cmake) 21 # Generate MlirConfig.cmake for the build tree. 24 set(MHLO_CONFIG_INCLUDE_EXPORTS "include(\"\${MHLO_CMAKE_DIR}/MHLOTargets.cmake\")") [all …]
|
/aosp_15_r20/prebuilts/cmake/linux-x86/share/cmake-3.22/Help/ |
D | index.rst | 17 This will detail the steps needed to run the :manual:`cmake(1)` or 18 :manual:`cmake-gui(1)` executable and how to choose a generator, and 25 is a suitable starting point. The :manual:`cmake-buildsystem(7)` 28 can be represented in CMake. The :manual:`cmake-packages(7)` manual 38 /manual/cmake.1 48 /manual/cmake-gui.1 57 /manual/cmake-buildsystem.7 58 /manual/cmake-commands.7 59 /manual/cmake-compile-features.7 60 /manual/cmake-developer.7 [all …]
|
12345678910>>...28