mirror of
https://github.com/crystalidea/qt-build-tools.git
synced 2025-07-05 08:55:24 +08:00
qr 6.5.1: still missed with cmake version, trying 3.18.3
This commit is contained in:
kleuter
@ -0,0 +1,5 @@
|
||||
ANDROID
|
||||
-------
|
||||
|
||||
Set to ``1`` when the target system (:variable:`CMAKE_SYSTEM_NAME`) is
|
||||
``Android``.
|
||||
@ -0,0 +1,5 @@
|
||||
APPLE
|
||||
-----
|
||||
|
||||
Set to ``True`` when the target system is an Apple platform
|
||||
(macOS, iOS, tvOS or watchOS).
|
||||
@ -0,0 +1,6 @@
|
||||
BORLAND
|
||||
-------
|
||||
|
||||
``True`` if the Borland compiler is being used.
|
||||
|
||||
This is set to ``true`` if the Borland compiler is being used.
|
||||
@ -0,0 +1,10 @@
|
||||
BUILD_SHARED_LIBS
|
||||
-----------------
|
||||
|
||||
Global flag to cause :command:`add_library` to create shared libraries if on.
|
||||
|
||||
If present and true, this will cause all libraries to be built shared
|
||||
unless the library was explicitly added as a static library. This
|
||||
variable is often added to projects as an :command:`option` so that each user
|
||||
of a project can decide if they want to build the project using shared or
|
||||
static libraries.
|
||||
18
6.5.1/_tools/cmake/share/cmake-3.18/Help/variable/CACHE.rst
Normal file
18
6.5.1/_tools/cmake/share/cmake-3.18/Help/variable/CACHE.rst
Normal file
@ -0,0 +1,18 @@
|
||||
CACHE
|
||||
-----
|
||||
|
||||
Operator to read cache variables.
|
||||
|
||||
Use the syntax ``$CACHE{VAR}`` to read cache entry ``VAR``.
|
||||
See the :ref:`cmake-language(7) variables <CMake Language Variables>`
|
||||
documentation for more complete documentation of the interaction of
|
||||
normal variables and cache entries.
|
||||
|
||||
When evaluating :ref:`Variable References` of the form ``${VAR}``,
|
||||
CMake first searches for a normal variable with that name, and if not
|
||||
found CMake will search for a cache entry with that name.
|
||||
The ``$CACHE{VAR}`` syntax can be used to do direct cache lookup and
|
||||
ignore any existing normal variable.
|
||||
|
||||
See the :command:`set` and :command:`unset` commands to see how to
|
||||
write or remove cache variables.
|
||||
@ -0,0 +1,9 @@
|
||||
CMAKE_ABSOLUTE_DESTINATION_FILES
|
||||
--------------------------------
|
||||
|
||||
List of files which have been installed using an ``ABSOLUTE DESTINATION`` path.
|
||||
|
||||
This variable is defined by CMake-generated ``cmake_install.cmake``
|
||||
scripts. It can be used (read-only) by programs or scripts that
|
||||
source those install scripts. This is used by some CPack generators
|
||||
(e.g. RPM).
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_AIX_EXPORT_ALL_SYMBOLS
|
||||
----------------------------
|
||||
|
||||
Default value for :prop_tgt:`AIX_EXPORT_ALL_SYMBOLS` target property.
|
||||
This variable is used to initialize the property on each target as it is
|
||||
created.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS
|
||||
------------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_ANT_ADDITIONAL_OPTIONS` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_ANDROID_API
|
||||
-----------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio
|
||||
Edition`, this variable may be set to specify the default value for the
|
||||
:prop_tgt:`ANDROID_API` target property. See that target property for
|
||||
additional information.
|
||||
|
||||
Otherwise, when :ref:`Cross Compiling for Android`, this variable provides
|
||||
the Android API version number targeted. This will be the same value as
|
||||
the :variable:`CMAKE_SYSTEM_VERSION` variable for ``Android`` platforms.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_API_MIN
|
||||
---------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_API_MIN` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,19 @@
|
||||
CMAKE_ANDROID_ARCH
|
||||
------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio
|
||||
Edition`, this variable may be set to specify the default value for the
|
||||
:prop_tgt:`ANDROID_ARCH` target property. See that target property for
|
||||
additional information.
|
||||
|
||||
Otherwise, when :ref:`Cross Compiling for Android`, this variable provides
|
||||
the name of the Android architecture corresponding to the value of the
|
||||
:variable:`CMAKE_ANDROID_ARCH_ABI` variable. The architecture name
|
||||
may be one of:
|
||||
|
||||
* ``arm``
|
||||
* ``arm64``
|
||||
* ``mips``
|
||||
* ``mips64``
|
||||
* ``x86``
|
||||
* ``x86_64``
|
||||
@ -0,0 +1,17 @@
|
||||
CMAKE_ANDROID_ARCH_ABI
|
||||
----------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android`, this variable specifies the
|
||||
target architecture and ABI to be used. Valid values are:
|
||||
|
||||
* ``arm64-v8a``
|
||||
* ``armeabi-v7a``
|
||||
* ``armeabi-v6``
|
||||
* ``armeabi``
|
||||
* ``mips``
|
||||
* ``mips64``
|
||||
* ``x86``
|
||||
* ``x86_64``
|
||||
|
||||
See also the :variable:`CMAKE_ANDROID_ARM_MODE` and
|
||||
:variable:`CMAKE_ANDROID_ARM_NEON` variables.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_ANDROID_ARM_MODE
|
||||
----------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android` and :variable:`CMAKE_ANDROID_ARCH_ABI`
|
||||
is set to one of the ``armeabi`` architectures, set ``CMAKE_ANDROID_ARM_MODE``
|
||||
to ``ON`` to target 32-bit ARM processors (``-marm``). Otherwise, the
|
||||
default is to target the 16-bit Thumb processors (``-mthumb``).
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_ANDROID_ARM_NEON
|
||||
----------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android` and :variable:`CMAKE_ANDROID_ARCH_ABI`
|
||||
is set to ``armeabi-v7a`` set ``CMAKE_ANDROID_ARM_NEON`` to ``ON`` to target
|
||||
ARM NEON devices.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_ASSETS_DIRECTORIES
|
||||
--------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_ASSETS_DIRECTORIES` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_GUI
|
||||
-----------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_GUI` target property of
|
||||
executables. See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_JAR_DEPENDENCIES
|
||||
------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_JAR_DEPENDENCIES` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_JAR_DIRECTORIES
|
||||
-----------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_JAR_DIRECTORIES` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_JAVA_SOURCE_DIR
|
||||
-----------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_JAVA_SOURCE_DIR` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES
|
||||
-------------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_NATIVE_LIB_DEPENDENCIES` target
|
||||
property. See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES
|
||||
------------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_NATIVE_LIB_DIRECTORIES` target
|
||||
property. See that target property for additional information.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_ANDROID_NDK
|
||||
-----------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with the NDK`, this variable holds
|
||||
the absolute path to the root directory of the NDK. The directory must
|
||||
contain a ``platforms`` subdirectory holding the ``android-<api>``
|
||||
directories.
|
||||
@ -0,0 +1,9 @@
|
||||
CMAKE_ANDROID_NDK_DEPRECATED_HEADERS
|
||||
------------------------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with the NDK`, this variable
|
||||
may be set to specify whether to use the deprecated per-api-level
|
||||
headers instead of the unified headers.
|
||||
|
||||
If not specified, the default will be *false* if using a NDK version
|
||||
that provides the unified headers and *true* otherwise.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG
|
||||
------------------------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with the NDK`, this variable
|
||||
provides the NDK's "host tag" used to construct the path to prebuilt
|
||||
toolchains that run on the host.
|
||||
@ -0,0 +1,20 @@
|
||||
CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION
|
||||
-----------------------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with the NDK`, this variable
|
||||
may be set to specify the version of the toolchain to be used
|
||||
as the compiler.
|
||||
|
||||
On NDK r19 or above, this variable must be unset or set to ``clang``.
|
||||
|
||||
On NDK r18 or below, this variable must be set to one of these forms:
|
||||
|
||||
* ``<major>.<minor>``: GCC of specified version
|
||||
* ``clang<major>.<minor>``: Clang of specified version
|
||||
* ``clang``: Clang of most recent available version
|
||||
|
||||
A toolchain of the requested version will be selected automatically to
|
||||
match the ABI named in the :variable:`CMAKE_ANDROID_ARCH_ABI` variable.
|
||||
|
||||
If not specified, the default will be a value that selects the latest
|
||||
available GCC toolchain.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_PROCESS_MAX
|
||||
-------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_PROCESS_MAX` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_PROGUARD
|
||||
----------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_PROGUARD` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_PROGUARD_CONFIG_PATH
|
||||
----------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_PROGUARD_CONFIG_PATH` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_SECURE_PROPS_PATH
|
||||
-------------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_SECURE_PROPS_PATH` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_ANDROID_SKIP_ANT_STEP
|
||||
---------------------------
|
||||
|
||||
Default value for the :prop_tgt:`ANDROID_SKIP_ANT_STEP` target property.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_ANDROID_STANDALONE_TOOLCHAIN
|
||||
----------------------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with a Standalone Toolchain`, this
|
||||
variable holds the absolute path to the root directory of the toolchain.
|
||||
The specified directory must contain a ``sysroot`` subdirectory.
|
||||
@ -0,0 +1,37 @@
|
||||
CMAKE_ANDROID_STL_TYPE
|
||||
----------------------
|
||||
|
||||
When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio
|
||||
Edition`, this variable may be set to specify the default value for the
|
||||
:prop_tgt:`ANDROID_STL_TYPE` target property. See that target property
|
||||
for additional information.
|
||||
|
||||
When :ref:`Cross Compiling for Android with the NDK`, this variable may be
|
||||
set to specify the STL variant to be used. The value may be one of:
|
||||
|
||||
``none``
|
||||
No C++ Support
|
||||
``system``
|
||||
Minimal C++ without STL
|
||||
``gabi++_static``
|
||||
GAbi++ Static
|
||||
``gabi++_shared``
|
||||
GAbi++ Shared
|
||||
``gnustl_static``
|
||||
GNU libstdc++ Static
|
||||
``gnustl_shared``
|
||||
GNU libstdc++ Shared
|
||||
``c++_static``
|
||||
LLVM libc++ Static
|
||||
``c++_shared``
|
||||
LLVM libc++ Shared
|
||||
``stlport_static``
|
||||
STLport Static
|
||||
``stlport_shared``
|
||||
STLport Shared
|
||||
|
||||
The default value is ``gnustl_static`` on NDK versions that provide it
|
||||
and otherwise ``c++_static``. Note that this default differs from
|
||||
the native NDK build system because CMake may be used to build projects for
|
||||
Android that are not natively implemented for it and use the C++ standard
|
||||
library.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_APPBUNDLE_PATH
|
||||
--------------------
|
||||
|
||||
:ref:`Semicolon-separated list <CMake Language Lists>` of directories specifying a search path
|
||||
for macOS application bundles used by the :command:`find_program`, and
|
||||
:command:`find_package` commands.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_AR
|
||||
--------
|
||||
|
||||
Name of archiving tool for static libraries.
|
||||
|
||||
This specifies the name of the program that creates archive or static
|
||||
libraries.
|
||||
@ -0,0 +1,9 @@
|
||||
CMAKE_ARCHIVE_OUTPUT_DIRECTORY
|
||||
------------------------------
|
||||
|
||||
Where to put all the :ref:`ARCHIVE <Archive Output Artifacts>`
|
||||
target files when built.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`ARCHIVE_OUTPUT_DIRECTORY`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
@ -0,0 +1,9 @@
|
||||
CMAKE_ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>
|
||||
---------------------------------------
|
||||
|
||||
Where to put all the :ref:`ARCHIVE <Archive Output Artifacts>`
|
||||
target files when built for a specific configuration.
|
||||
|
||||
This variable is used to initialize the
|
||||
:prop_tgt:`ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>` property on all the targets.
|
||||
See that target property for additional information.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_ARGC
|
||||
----------
|
||||
|
||||
Number of command line arguments passed to CMake in script mode.
|
||||
|
||||
When run in :ref:`-P <Script Processing Mode>` script mode, CMake sets this
|
||||
variable to the number of command line arguments. See also
|
||||
:variable:`CMAKE_ARGV0`, ``1``, ``2`` ...
|
||||
@ -0,0 +1,9 @@
|
||||
CMAKE_ARGV0
|
||||
-----------
|
||||
|
||||
Command line argument passed to CMake in script mode.
|
||||
|
||||
When run in :ref:`-P <Script Processing Mode>` script mode, CMake sets this
|
||||
variable to the first command line argument. It then also sets ``CMAKE_ARGV1``,
|
||||
``CMAKE_ARGV2``, ... and so on, up to the number of command line arguments
|
||||
given. See also :variable:`CMAKE_ARGC`.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_AUTOGEN_ORIGIN_DEPENDS
|
||||
----------------------------
|
||||
|
||||
Switch for forwarding origin target dependencies to the corresponding
|
||||
``_autogen`` targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
|
||||
By default :variable:`CMAKE_AUTOGEN_ORIGIN_DEPENDS` is ``ON``.
|
||||
@ -0,0 +1,10 @@
|
||||
CMAKE_AUTOGEN_PARALLEL
|
||||
----------------------
|
||||
|
||||
Number of parallel ``moc`` or ``uic`` processes to start when using
|
||||
:prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOGEN_PARALLEL` property
|
||||
on all the targets. See that target property for additional information.
|
||||
|
||||
By default :variable:`CMAKE_AUTOGEN_PARALLEL` is unset.
|
||||
@ -0,0 +1,13 @@
|
||||
CMAKE_AUTOGEN_VERBOSE
|
||||
---------------------
|
||||
|
||||
Sets the verbosity of :prop_tgt:`AUTOMOC`, :prop_tgt:`AUTOUIC` and
|
||||
:prop_tgt:`AUTORCC`. A positive integer value or a true boolean value
|
||||
lets the ``AUTO*`` generators output additional processing information.
|
||||
|
||||
Setting :variable:`CMAKE_AUTOGEN_VERBOSE` has the same effect
|
||||
as setting the ``VERBOSE`` environment variable during
|
||||
generation (e.g. by calling ``make VERBOSE=1``).
|
||||
The extra verbosity is limited to the ``AUTO*`` generators though.
|
||||
|
||||
By default :variable:`CMAKE_AUTOGEN_VERBOSE` is unset.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_AUTOMOC
|
||||
-------------
|
||||
|
||||
Whether to handle ``moc`` automatically for Qt targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOMOC` property on all the
|
||||
targets. See that target property for additional information.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_AUTOMOC_COMPILER_PREDEFINES
|
||||
---------------------------------
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOMOC_COMPILER_PREDEFINES`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
|
||||
By default it is ON.
|
||||
@ -0,0 +1,12 @@
|
||||
CMAKE_AUTOMOC_DEPEND_FILTERS
|
||||
----------------------------
|
||||
|
||||
Filter definitions used by :variable:`CMAKE_AUTOMOC`
|
||||
to extract file names from source code as additional dependencies
|
||||
for the ``moc`` file.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOMOC_DEPEND_FILTERS`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
|
||||
By default it is empty.
|
||||
@ -0,0 +1,20 @@
|
||||
CMAKE_AUTOMOC_MACRO_NAMES
|
||||
----------------------------
|
||||
|
||||
:ref:`Semicolon-separated list <CMake Language Lists>` list of macro names used by
|
||||
:variable:`CMAKE_AUTOMOC` to determine if a C++ file needs to be
|
||||
processed by ``moc``.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOMOC_MACRO_NAMES`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
|
||||
The default value is ``Q_OBJECT;Q_GADGET;Q_NAMESPACE``.
|
||||
|
||||
Example
|
||||
^^^^^^^
|
||||
Let CMake know that source files that contain ``CUSTOM_MACRO`` must be ``moc``
|
||||
processed as well::
|
||||
|
||||
set(CMAKE_AUTOMOC ON)
|
||||
list(APPEND CMAKE_AUTOMOC_MACRO_NAMES "CUSTOM_MACRO")
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_AUTOMOC_MOC_OPTIONS
|
||||
-------------------------
|
||||
|
||||
Additional options for ``moc`` when using :variable:`CMAKE_AUTOMOC`.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOMOC_MOC_OPTIONS` property
|
||||
on all the targets. See that target property for additional information.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_AUTOMOC_PATH_PREFIX
|
||||
-------------------------
|
||||
|
||||
Whether to generate the ``-p`` path prefix option for ``moc`` on
|
||||
:prop_tgt:`AUTOMOC` enabled Qt targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOMOC_PATH_PREFIX`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
|
||||
The default value is ``OFF``.
|
||||
@ -0,0 +1,15 @@
|
||||
CMAKE_AUTOMOC_RELAXED_MODE
|
||||
--------------------------
|
||||
|
||||
.. deprecated:: 3.15
|
||||
|
||||
Switch between strict and relaxed automoc mode.
|
||||
|
||||
By default, :prop_tgt:`AUTOMOC` behaves exactly as described in the
|
||||
documentation of the :prop_tgt:`AUTOMOC` target property. When set to
|
||||
``TRUE``, it accepts more input and tries to find the correct input file for
|
||||
``moc`` even if it differs from the documented behaviour. In this mode it
|
||||
e.g. also checks whether a header file is intended to be processed by moc
|
||||
when a ``"foo.moc"`` file has been included.
|
||||
|
||||
Relaxed mode has to be enabled for KDE4 compatibility.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_AUTORCC
|
||||
-------------
|
||||
|
||||
Whether to handle ``rcc`` automatically for Qt targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTORCC` property on all
|
||||
the targets. See that target property for additional information.
|
||||
@ -0,0 +1,16 @@
|
||||
CMAKE_AUTORCC_OPTIONS
|
||||
---------------------
|
||||
|
||||
Additional options for ``rcc`` when using :variable:`CMAKE_AUTORCC`.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTORCC_OPTIONS` property on
|
||||
all the targets. See that target property for additional information.
|
||||
|
||||
EXAMPLE
|
||||
^^^^^^^
|
||||
|
||||
.. code-block:: cmake
|
||||
|
||||
# ...
|
||||
set(CMAKE_AUTORCC_OPTIONS "--compress;9")
|
||||
# ...
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_AUTOUIC
|
||||
-------------
|
||||
|
||||
Whether to handle ``uic`` automatically for Qt targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOUIC` property on all
|
||||
the targets. See that target property for additional information.
|
||||
@ -0,0 +1,16 @@
|
||||
CMAKE_AUTOUIC_OPTIONS
|
||||
---------------------
|
||||
|
||||
Additional options for ``uic`` when using :variable:`CMAKE_AUTOUIC`.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOUIC_OPTIONS` property on
|
||||
all the targets. See that target property for additional information.
|
||||
|
||||
EXAMPLE
|
||||
^^^^^^^
|
||||
|
||||
.. code-block:: cmake
|
||||
|
||||
# ...
|
||||
set_property(CMAKE_AUTOUIC_OPTIONS "--no-protection")
|
||||
# ...
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_AUTOUIC_SEARCH_PATHS
|
||||
--------------------------
|
||||
|
||||
Search path list used by :variable:`CMAKE_AUTOUIC` to find included
|
||||
``.ui`` files.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`AUTOUIC_SEARCH_PATHS`
|
||||
property on all the targets. See that target property for additional
|
||||
information.
|
||||
|
||||
By default it is empty.
|
||||
@ -0,0 +1,4 @@
|
||||
CMAKE_BACKWARDS_COMPATIBILITY
|
||||
-----------------------------
|
||||
|
||||
Deprecated. See CMake Policy :policy:`CMP0001` documentation.
|
||||
@ -0,0 +1,13 @@
|
||||
CMAKE_BINARY_DIR
|
||||
----------------
|
||||
|
||||
The path to the top level of the build tree.
|
||||
|
||||
This is the full path to the top level of the current CMake build
|
||||
tree. For an in-source build, this would be the same as
|
||||
:variable:`CMAKE_SOURCE_DIR`.
|
||||
|
||||
When run in -P script mode, CMake sets the variables
|
||||
:variable:`CMAKE_BINARY_DIR`, :variable:`CMAKE_SOURCE_DIR`,
|
||||
:variable:`CMAKE_CURRENT_BINARY_DIR` and
|
||||
:variable:`CMAKE_CURRENT_SOURCE_DIR` to the current working directory.
|
||||
@ -0,0 +1,10 @@
|
||||
CMAKE_BUILD_RPATH
|
||||
-----------------
|
||||
|
||||
:ref:`Semicolon-separated list <CMake Language Lists>` specifying runtime path (``RPATH``)
|
||||
entries to add to binaries linked in the build tree (for platforms that
|
||||
support it). The entries will *not* be used for binaries in the install
|
||||
tree. See also the :variable:`CMAKE_INSTALL_RPATH` variable.
|
||||
|
||||
This is used to initialize the :prop_tgt:`BUILD_RPATH` target property
|
||||
for all targets.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_BUILD_RPATH_USE_ORIGIN
|
||||
----------------------------
|
||||
|
||||
Whether to use relative paths for the build ``RPATH``.
|
||||
|
||||
This is used to initialize the :prop_tgt:`BUILD_RPATH_USE_ORIGIN` target
|
||||
property for all targets, see that property for more details.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_BUILD_TOOL
|
||||
----------------
|
||||
|
||||
This variable exists only for backwards compatibility.
|
||||
It contains the same value as :variable:`CMAKE_MAKE_PROGRAM`.
|
||||
Use that variable instead.
|
||||
@ -0,0 +1,20 @@
|
||||
CMAKE_BUILD_TYPE
|
||||
----------------
|
||||
|
||||
Specifies the build type on single-configuration generators.
|
||||
|
||||
This statically specifies what build type (configuration) will be
|
||||
built in this build tree. Possible values are empty, ``Debug``, ``Release``,
|
||||
``RelWithDebInfo``, ``MinSizeRel``, ... This variable is only meaningful to
|
||||
single-configuration generators (such as :ref:`Makefile Generators` and
|
||||
:generator:`Ninja`) i.e. those which choose a single configuration when CMake
|
||||
runs to generate a build tree as opposed to multi-configuration generators
|
||||
which offer selection of the build configuration within the generated build
|
||||
environment. There are many per-config properties and variables
|
||||
(usually following clean ``SOME_VAR_<CONFIG>`` order conventions), such as
|
||||
``CMAKE_C_FLAGS_<CONFIG>``, specified as uppercase:
|
||||
``CMAKE_C_FLAGS_[DEBUG|RELEASE|RELWITHDEBINFO|MINSIZEREL|...]``. For example,
|
||||
in a build tree configured to build type ``Debug``, CMake will see to
|
||||
having :variable:`CMAKE_C_FLAGS_DEBUG <CMAKE_<LANG>_FLAGS_DEBUG>` settings get
|
||||
added to the :variable:`CMAKE_C_FLAGS <CMAKE_<LANG>_FLAGS>` settings. See
|
||||
also :variable:`CMAKE_CONFIGURATION_TYPES`.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_BUILD_WITH_INSTALL_NAME_DIR
|
||||
---------------------------------
|
||||
|
||||
Whether to use :prop_tgt:`INSTALL_NAME_DIR` on targets in the build tree.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`BUILD_WITH_INSTALL_NAME_DIR`
|
||||
property on all targets.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_BUILD_WITH_INSTALL_RPATH
|
||||
------------------------------
|
||||
|
||||
Use the install path for the ``RPATH``.
|
||||
|
||||
Normally CMake uses the build tree for the ``RPATH`` when building
|
||||
executables etc on systems that use ``RPATH``. When the software is
|
||||
installed the executables etc are relinked by CMake to have the
|
||||
install ``RPATH``. If this variable is set to true then the software is
|
||||
always built with the install path for the ``RPATH`` and does not need to
|
||||
be relinked when installed.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_CACHEFILE_DIR
|
||||
-------------------
|
||||
|
||||
The directory with the ``CMakeCache.txt`` file.
|
||||
|
||||
This is the full path to the directory that has the ``CMakeCache.txt``
|
||||
file in it. This is the same as :variable:`CMAKE_BINARY_DIR`.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CACHE_MAJOR_VERSION
|
||||
-------------------------
|
||||
|
||||
Major version of CMake used to create the ``CMakeCache.txt`` file
|
||||
|
||||
This stores the major version of CMake used to write a CMake cache
|
||||
file. It is only different when a different version of CMake is run
|
||||
on a previously created cache file.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CACHE_MINOR_VERSION
|
||||
-------------------------
|
||||
|
||||
Minor version of CMake used to create the ``CMakeCache.txt`` file
|
||||
|
||||
This stores the minor version of CMake used to write a CMake cache
|
||||
file. It is only different when a different version of CMake is run
|
||||
on a previously created cache file.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CACHE_PATCH_VERSION
|
||||
-------------------------
|
||||
|
||||
Patch version of CMake used to create the ``CMakeCache.txt`` file
|
||||
|
||||
This stores the patch version of CMake used to write a CMake cache
|
||||
file. It is only different when a different version of CMake is run
|
||||
on a previously created cache file.
|
||||
@ -0,0 +1,52 @@
|
||||
CMAKE_CFG_INTDIR
|
||||
----------------
|
||||
|
||||
Build-time reference to per-configuration output subdirectory.
|
||||
|
||||
For native build systems supporting multiple configurations in the
|
||||
build tree (such as :ref:`Visual Studio Generators` and :generator:`Xcode`),
|
||||
the value is a reference to a build-time variable specifying the name
|
||||
of the per-configuration output subdirectory. On :ref:`Makefile Generators`
|
||||
this evaluates to `.` because there is only one configuration in a build tree.
|
||||
Example values:
|
||||
|
||||
::
|
||||
|
||||
$(ConfigurationName) = Visual Studio 9
|
||||
$(Configuration) = Visual Studio 10
|
||||
$(CONFIGURATION) = Xcode
|
||||
. = Make-based tools
|
||||
. = Ninja
|
||||
${CONFIGURATION} = Ninja Multi-Config
|
||||
|
||||
Note that this variable only has limited support on
|
||||
:generator:`Ninja Multi-Config`. It is recommended that you use the
|
||||
``$<CONFIG>`` :manual:`generator expression <cmake-generator-expressions(7)>`
|
||||
instead.
|
||||
|
||||
Since these values are evaluated by the native build system, this
|
||||
variable is suitable only for use in command lines that will be
|
||||
evaluated at build time. Example of intended usage:
|
||||
|
||||
::
|
||||
|
||||
add_executable(mytool mytool.c)
|
||||
add_custom_command(
|
||||
OUTPUT out.txt
|
||||
COMMAND ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool
|
||||
${CMAKE_CURRENT_SOURCE_DIR}/in.txt out.txt
|
||||
DEPENDS mytool in.txt
|
||||
)
|
||||
add_custom_target(drive ALL DEPENDS out.txt)
|
||||
|
||||
Note that ``CMAKE_CFG_INTDIR`` is no longer necessary for this purpose but
|
||||
has been left for compatibility with existing projects. Instead
|
||||
:command:`add_custom_command` recognizes executable target names in its
|
||||
``COMMAND`` option, so
|
||||
``${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool`` can be replaced
|
||||
by just ``mytool``.
|
||||
|
||||
This variable is read-only. Setting it is undefined behavior. In
|
||||
multi-configuration build systems the value of this variable is passed
|
||||
as the value of preprocessor symbol ``CMAKE_INTDIR`` to the compilation
|
||||
of all source files.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_CL_64
|
||||
-----------
|
||||
|
||||
Discouraged. Use :variable:`CMAKE_SIZEOF_VOID_P` instead.
|
||||
|
||||
Set to a true value when using a Microsoft Visual Studio ``cl`` compiler that
|
||||
*targets* a 64-bit architecture.
|
||||
@ -0,0 +1,13 @@
|
||||
CMAKE_CODEBLOCKS_COMPILER_ID
|
||||
----------------------------
|
||||
|
||||
Change the compiler id in the generated CodeBlocks project files.
|
||||
|
||||
CodeBlocks uses its own compiler id string which differs from
|
||||
:variable:`CMAKE_<LANG>_COMPILER_ID`. If this variable is left empty,
|
||||
CMake tries to recognize the CodeBlocks compiler id automatically.
|
||||
Otherwise the specified string is used in the CodeBlocks project file.
|
||||
See the CodeBlocks documentation for valid compiler id strings.
|
||||
|
||||
Other IDEs like QtCreator that also use the CodeBlocks generator may ignore
|
||||
this setting.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES
|
||||
---------------------------------------
|
||||
|
||||
Change the way the CodeBlocks generator creates project files.
|
||||
|
||||
If this variable evaluates to ``ON`` the generator excludes from
|
||||
the project file any files that are located outside the project root.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CODELITE_USE_TARGETS
|
||||
--------------------------
|
||||
|
||||
Change the way the CodeLite generator creates projectfiles.
|
||||
|
||||
If this variable evaluates to ``ON`` at the end of the top-level
|
||||
``CMakeLists.txt`` file, the generator creates projectfiles based on targets
|
||||
rather than projects.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_COLOR_MAKEFILE
|
||||
--------------------
|
||||
|
||||
Enables color output when using the :ref:`Makefile Generators`.
|
||||
|
||||
When enabled, the generated Makefiles will produce colored output.
|
||||
Default is ``ON``.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_COMMAND
|
||||
-------------
|
||||
|
||||
The full path to the :manual:`cmake(1)` executable.
|
||||
|
||||
This is the full path to the CMake executable :manual:`cmake(1)` which is
|
||||
useful from custom commands that want to use the ``cmake -E`` option for
|
||||
portable system commands. (e.g. ``/usr/local/bin/cmake``)
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_COMPILER_2005
|
||||
-------------------
|
||||
|
||||
Using the Visual Studio 2005 compiler from Microsoft
|
||||
|
||||
Set to true when using the Visual Studio 2005 compiler from Microsoft.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_COMPILER_IS_GNUCC
|
||||
-----------------------
|
||||
|
||||
True if the ``C`` compiler is GNU.
|
||||
Use :variable:`CMAKE_C_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` instead.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_COMPILER_IS_GNUCXX
|
||||
------------------------
|
||||
|
||||
True if the C++ (``CXX``) compiler is GNU.
|
||||
Use :variable:`CMAKE_CXX_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` instead.
|
||||
@ -0,0 +1,5 @@
|
||||
CMAKE_COMPILER_IS_GNUG77
|
||||
------------------------
|
||||
|
||||
True if the ``Fortran`` compiler is GNU.
|
||||
Use :variable:`CMAKE_Fortran_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` instead.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY
|
||||
----------------------------------
|
||||
|
||||
Output directory for MS debug symbol ``.pdb`` files
|
||||
generated by the compiler while building source files.
|
||||
|
||||
This variable is used to initialize the
|
||||
:prop_tgt:`COMPILE_PDB_OUTPUT_DIRECTORY` property on all the targets.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>
|
||||
-------------------------------------------
|
||||
|
||||
Per-configuration output directory for MS debug symbol ``.pdb`` files
|
||||
generated by the compiler while building source files.
|
||||
|
||||
This is a per-configuration version of
|
||||
:variable:`CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY`.
|
||||
This variable is used to initialize the
|
||||
:prop_tgt:`COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>`
|
||||
property on all the targets.
|
||||
@ -0,0 +1,10 @@
|
||||
CMAKE_CONFIGURATION_TYPES
|
||||
-------------------------
|
||||
|
||||
Specifies the available build types on multi-config generators.
|
||||
|
||||
This specifies what build types (configurations) will be available
|
||||
such as ``Debug``, ``Release``, ``RelWithDebInfo`` etc. This has reasonable
|
||||
defaults on most platforms, but can be extended to provide other build
|
||||
types. See also :variable:`CMAKE_BUILD_TYPE` for details of managing
|
||||
configuration data, and :variable:`CMAKE_CFG_INTDIR`.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_<CONFIG>_POSTFIX
|
||||
----------------------
|
||||
|
||||
Default filename postfix for libraries under configuration ``<CONFIG>``.
|
||||
|
||||
When a non-executable target is created its :prop_tgt:`<CONFIG>_POSTFIX`
|
||||
target property is initialized with the value of this variable if it is set.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CPACK_COMMAND
|
||||
-------------------
|
||||
|
||||
Full path to :manual:`cpack(1)` command installed with CMake.
|
||||
|
||||
This is the full path to the CPack executable :manual:`cpack(1)` which is
|
||||
useful from custom commands that want to use the :manual:`cmake(1)` ``-E``
|
||||
option for portable system commands.
|
||||
@ -0,0 +1,27 @@
|
||||
CMAKE_CROSSCOMPILING
|
||||
--------------------
|
||||
|
||||
Intended to indicate whether CMake is cross compiling, but note limitations
|
||||
discussed below.
|
||||
|
||||
This variable will be set to true by CMake if the :variable:`CMAKE_SYSTEM_NAME`
|
||||
variable has been set manually (i.e. in a toolchain file or as a cache entry
|
||||
from the :manual:`cmake <cmake(1)>` command line). In most cases, manually
|
||||
setting :variable:`CMAKE_SYSTEM_NAME` will only be done when cross compiling,
|
||||
since it will otherwise be given the same value as
|
||||
:variable:`CMAKE_HOST_SYSTEM_NAME` if not manually set, which is correct for
|
||||
the non-cross-compiling case. In the event that :variable:`CMAKE_SYSTEM_NAME`
|
||||
is manually set to the same value as :variable:`CMAKE_HOST_SYSTEM_NAME`, then
|
||||
``CMAKE_CROSSCOMPILING`` will still be set to true.
|
||||
|
||||
Another case to be aware of is that builds targeting Apple platforms other than
|
||||
macOS are handled differently to other cross compiling scenarios. Rather than
|
||||
relying on :variable:`CMAKE_SYSTEM_NAME` to select the target platform, Apple
|
||||
device builds use :variable:`CMAKE_OSX_SYSROOT` to select the appropriate SDK,
|
||||
which indirectly determines the target platform. Furthermore, when using the
|
||||
:generator:`Xcode` generator, developers can switch between device and
|
||||
simulator builds at build time rather than having a single
|
||||
choice at configure time, so the concept
|
||||
of whether the build is cross compiling or not is more complex. Therefore, the
|
||||
use of ``CMAKE_CROSSCOMPILING`` is not recommended for projects targeting Apple
|
||||
devices.
|
||||
@ -0,0 +1,16 @@
|
||||
CMAKE_CROSSCOMPILING_EMULATOR
|
||||
-----------------------------
|
||||
|
||||
This variable is only used when :variable:`CMAKE_CROSSCOMPILING` is on. It
|
||||
should point to a command on the host system that can run executable built
|
||||
for the target system.
|
||||
|
||||
If this variable contains a :ref:`semicolon-separated list <CMake Language
|
||||
Lists>`, then the first value is the command and remaining values are its
|
||||
arguments.
|
||||
|
||||
The command will be used to run :command:`try_run` generated executables,
|
||||
which avoids manual population of the ``TryRunResults.cmake`` file.
|
||||
|
||||
It is also used as the default value for the
|
||||
:prop_tgt:`CROSSCOMPILING_EMULATOR` target property of executables.
|
||||
@ -0,0 +1,15 @@
|
||||
CMAKE_CROSS_CONFIGS
|
||||
-------------------
|
||||
|
||||
Specifies a :ref:`semicolon-separated list <CMake Language Lists>` of
|
||||
configurations available from all ``build-<Config>.ninja`` files in the
|
||||
:generator:`Ninja Multi-Config` generator. This variable activates
|
||||
cross-config mode. Targets from each config specified in this variable can be
|
||||
built from any ``build-<Config>.ninja`` file. Custom commands will use the
|
||||
configuration native to ``build-<Config>.ninja``. If it is set to ``all``, all
|
||||
configurations from :variable:`CMAKE_CONFIGURATION_TYPES` are cross-configs. If
|
||||
it is not specified, or empty, each ``build-<Config>.ninja`` file will only
|
||||
contain build rules for its own configuration.
|
||||
|
||||
The value of this variable must be a subset of
|
||||
:variable:`CMAKE_CONFIGURATION_TYPES`.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_CTEST_ARGUMENTS
|
||||
---------------------
|
||||
|
||||
Set this to a :ref:`semicolon-separated list <CMake Language Lists>` of
|
||||
command-line arguments to pass to :manual:`ctest(1)` when running tests
|
||||
through the ``test`` (or ``RUN_TESTS``) target of the generated build system.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CTEST_COMMAND
|
||||
-------------------
|
||||
|
||||
Full path to :manual:`ctest(1)` command installed with CMake.
|
||||
|
||||
This is the full path to the CTest executable :manual:`ctest(1)` which is
|
||||
useful from custom commands that want to use the :manual:`cmake(1)` ``-E``
|
||||
option for portable system commands.
|
||||
@ -0,0 +1,17 @@
|
||||
CMAKE_CUDA_ARCHITECTURES
|
||||
------------------------
|
||||
|
||||
Default value for :prop_tgt:`CUDA_ARCHITECTURES` property of targets.
|
||||
|
||||
This is initialized as follows depending on :variable:`CMAKE_CUDA_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>`:
|
||||
|
||||
- For ``Clang``: the oldest architecture that works.
|
||||
|
||||
- For ``NVIDIA``: the default architecture chosen by the compiler.
|
||||
See policy :policy:`CMP0104`.
|
||||
|
||||
Users are encouraged to override this, as the default varies across compilers
|
||||
and compiler versions.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`CUDA_ARCHITECTURES` property
|
||||
on all targets. See the target property for additional information.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_CUDA_COMPILE_FEATURES
|
||||
---------------------------
|
||||
|
||||
List of features known to the CUDA compiler
|
||||
|
||||
These features are known to be available for use with the CUDA compiler. This
|
||||
list is a subset of the features listed in the
|
||||
:prop_gbl:`CMAKE_CUDA_KNOWN_FEATURES` global property.
|
||||
|
||||
See the :manual:`cmake-compile-features(7)` manual for information on
|
||||
compile features and a list of supported compilers.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_CUDA_EXTENSIONS
|
||||
---------------------
|
||||
|
||||
Default value for :prop_tgt:`CUDA_EXTENSIONS` property of targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`CUDA_EXTENSIONS`
|
||||
property on all targets. See that target property for additional
|
||||
information.
|
||||
|
||||
See the :manual:`cmake-compile-features(7)` manual for information on
|
||||
compile features and a list of supported compilers.
|
||||
@ -0,0 +1,8 @@
|
||||
CMAKE_CUDA_HOST_COMPILER
|
||||
------------------------
|
||||
|
||||
Executable to use when compiling host code when compiling ``CUDA`` language
|
||||
files. Maps to the ``nvcc -ccbin`` option. Will only be used by CMake on the first
|
||||
configuration to determine a valid host compiler for ``CUDA``. After a valid
|
||||
host compiler has been found, this value is read-only. This variable takes
|
||||
priority over the :envvar:`CUDAHOSTCXX` environment variable.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS
|
||||
---------------------------------
|
||||
|
||||
Default value for :prop_tgt:`CUDA_RESOLVE_DEVICE_SYMBOLS` target
|
||||
property. This variable is used to initialize the property on each target as
|
||||
it is created.
|
||||
@ -0,0 +1,25 @@
|
||||
CMAKE_CUDA_RUNTIME_LIBRARY
|
||||
--------------------------
|
||||
|
||||
Select the CUDA runtime library for use when compiling and linking CUDA.
|
||||
This variable is used to initialize the :prop_tgt:`CUDA_RUNTIME_LIBRARY`
|
||||
property on all targets as they are created.
|
||||
|
||||
The allowed case insensitive values are:
|
||||
|
||||
.. include:: ../prop_tgt/CUDA_RUNTIME_LIBRARY-VALUES.txt
|
||||
|
||||
Contents of ``CMAKE_CUDA_RUNTIME_LIBRARY`` may use
|
||||
:manual:`generator expressions <cmake-generator-expressions(7)>`.
|
||||
|
||||
If this variable is not set then the :prop_tgt:`CUDA_RUNTIME_LIBRARY` target
|
||||
property will not be set automatically. If that property is not set then
|
||||
CMake uses an appropriate default value based on the compiler to select the
|
||||
CUDA runtime library.
|
||||
|
||||
.. note::
|
||||
|
||||
This property has effect only when the ``CUDA`` language is enabled. To
|
||||
control the CUDA runtime linking when only using the CUDA SDK with the
|
||||
``C`` or ``C++`` language we recommend using the :module:`FindCUDAToolkit`
|
||||
module.
|
||||
@ -0,0 +1,6 @@
|
||||
CMAKE_CUDA_SEPARABLE_COMPILATION
|
||||
--------------------------------
|
||||
|
||||
Default value for :prop_tgt:`CUDA_SEPARABLE_COMPILATION` target property.
|
||||
This variable is used to initialize the property on each target as it is
|
||||
created.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_CUDA_STANDARD
|
||||
-------------------
|
||||
|
||||
Default value for :prop_tgt:`CUDA_STANDARD` property of targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`CUDA_STANDARD`
|
||||
property on all targets. See that target property for additional
|
||||
information.
|
||||
|
||||
See the :manual:`cmake-compile-features(7)` manual for information on
|
||||
compile features and a list of supported compilers.
|
||||
@ -0,0 +1,11 @@
|
||||
CMAKE_CUDA_STANDARD_REQUIRED
|
||||
----------------------------
|
||||
|
||||
Default value for :prop_tgt:`CUDA_STANDARD_REQUIRED` property of targets.
|
||||
|
||||
This variable is used to initialize the :prop_tgt:`CUDA_STANDARD_REQUIRED`
|
||||
property on all targets. See that target property for additional
|
||||
information.
|
||||
|
||||
See the :manual:`cmake-compile-features(7)` manual for information on
|
||||
compile features and a list of supported compilers.
|
||||
@ -0,0 +1,7 @@
|
||||
CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES
|
||||
--------------------------------------
|
||||
|
||||
When the ``CUDA`` language has been enabled, this provides a
|
||||
:ref:`semicolon-separated list <CMake Language Lists>` of include directories provided
|
||||
by the CUDA Toolkit. The value may be useful for C++ source files
|
||||
to include CUDA headers.
|
||||
@ -0,0 +1,15 @@
|
||||
CMAKE_CURRENT_BINARY_DIR
|
||||
------------------------
|
||||
|
||||
The path to the binary directory currently being processed.
|
||||
|
||||
This the full path to the build directory that is currently being
|
||||
processed by cmake. Each directory added by :command:`add_subdirectory` will
|
||||
create a binary directory in the build tree, and as it is being
|
||||
processed this variable will be set. For in-source builds this is the
|
||||
current source directory being processed.
|
||||
|
||||
When run in -P script mode, CMake sets the variables
|
||||
:variable:`CMAKE_BINARY_DIR`, :variable:`CMAKE_SOURCE_DIR`,
|
||||
:variable:`CMAKE_CURRENT_BINARY_DIR` and
|
||||
:variable:`CMAKE_CURRENT_SOURCE_DIR` to the current working directory.
|
||||
@ -0,0 +1,10 @@
|
||||
CMAKE_CURRENT_FUNCTION
|
||||
----------------------
|
||||
|
||||
When executing code inside a :command:`function`, this variable
|
||||
contains the name of the current function. It can be useful for
|
||||
diagnostic or debug messages.
|
||||
|
||||
See also :variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR`,
|
||||
:variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE` and
|
||||
:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE`.
|
||||
@ -0,0 +1,41 @@
|
||||
CMAKE_CURRENT_FUNCTION_LIST_DIR
|
||||
-------------------------------
|
||||
|
||||
When executing code inside a :command:`function`, this variable
|
||||
contains the full directory of the listfile that defined the current function.
|
||||
|
||||
It is quite common practice in CMake for modules to use some additional files,
|
||||
such as templates to be copied in after substituting CMake variables.
|
||||
In such cases, a function needs to know where to locate those files in a way
|
||||
that doesn't depend on where the function is called. Without
|
||||
``CMAKE_CURRENT_FUNCTION_LIST_DIR``, the code to do that would typically use
|
||||
the following pattern:
|
||||
|
||||
.. code-block:: cmake
|
||||
|
||||
set(_THIS_MODULE_BASE_DIR "${CMAKE_CURRENT_LIST_DIR}")
|
||||
|
||||
function(foo)
|
||||
configure_file(
|
||||
"${_THIS_MODULE_BASE_DIR}/some.template.in"
|
||||
some.output
|
||||
)
|
||||
endfunction()
|
||||
|
||||
Using ``CMAKE_CURRENT_FUNCTION_LIST_DIR`` inside the function instead
|
||||
eliminates the need for the extra variable which would otherwise be visible
|
||||
outside the function's scope.
|
||||
The above example can be written in the more concise and more robust form:
|
||||
|
||||
.. code-block:: cmake
|
||||
|
||||
function(foo)
|
||||
configure_file(
|
||||
"${CMAKE_CURRENT_FUNCTION_LIST_DIR}/some.template.in"
|
||||
some.output
|
||||
)
|
||||
endfunction()
|
||||
|
||||
See also :variable:`CMAKE_CURRENT_FUNCTION`,
|
||||
:variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE` and
|
||||
:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE`.
|
||||
@ -0,0 +1,9 @@
|
||||
CMAKE_CURRENT_FUNCTION_LIST_FILE
|
||||
--------------------------------
|
||||
|
||||
When executing code inside a :command:`function`, this variable
|
||||
contains the full path to the listfile that defined the current function.
|
||||
|
||||
See also :variable:`CMAKE_CURRENT_FUNCTION`,
|
||||
:variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR` and
|
||||
:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE`.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user