summaryrefslogtreecommitdiff
path: root/Help/prop_tgt/COMPILE_DEFINITIONS.rst
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2013-10-07 11:10:21 -0400
committerBrad King <brad.king@kitware.com>2013-10-16 09:22:38 -0400
commite7ca48f226782e7354a7ea9d6f9cef58e8773306 (patch)
tree537ac62cfb935bddafd3e0084c67d3ca7cc5196d /Help/prop_tgt/COMPILE_DEFINITIONS.rst
parent97e8650d7bd213e5fde721a0f7d71b63ac238370 (diff)
downloadcmake-e7ca48f226782e7354a7ea9d6f9cef58e8773306.tar.gz
Help: Factor out cmake-generator-expressions manual page
Generator expressions are supported in many places and are a distinct concept worthy of their own manual page. The old builtin documentation was previously represented by preprocessor macros to generate it into each place that supports them. Factor out the duplicate content into a dedicated cmake-generator-expressions manual page and reference it from each original location.
Diffstat (limited to 'Help/prop_tgt/COMPILE_DEFINITIONS.rst')
-rw-r--r--Help/prop_tgt/COMPILE_DEFINITIONS.rst78
1 files changed, 3 insertions, 75 deletions
diff --git a/Help/prop_tgt/COMPILE_DEFINITIONS.rst b/Help/prop_tgt/COMPILE_DEFINITIONS.rst
index b6999fcaa7..51bdb925f0 100644
--- a/Help/prop_tgt/COMPILE_DEFINITIONS.rst
+++ b/Help/prop_tgt/COMPILE_DEFINITIONS.rst
@@ -16,80 +16,8 @@ CMake will automatically drop some definitions that are not supported
by the native build tool. The VS6 IDE does not support definition
values with spaces (but NMake does).
-Contents of COMPILE_DEFINITIONS may use "generator expressions" with
-the syntax "$<...>". Generator expressions are evaluated during build
-system generation to produce information specific to each build
-configuration. Valid expressions are:
-
-::
-
- $<0:...> = empty string (ignores "...")
- $<1:...> = content of "..."
- $<CONFIG:cfg> = '1' if config is "cfg", else '0'
- $<CONFIGURATION> = configuration name
- $<BOOL:...> = '1' if the '...' is true, else '0'
- $<STREQUAL:a,b> = '1' if a is STREQUAL b, else '0'
- $<ANGLE-R> = A literal '>'. Used to compare strings which contain a '>' for example.
- $<COMMA> = A literal ','. Used to compare strings which contain a ',' for example.
- $<SEMICOLON> = A literal ';'. Used to prevent list expansion on an argument with ';'.
- $<JOIN:list,...> = joins the list with the content of "..."
- $<TARGET_NAME:...> = Marks ... as being the name of a target. This is required if exporting targets to multiple dependent export sets. The '...' must be a literal name of a target- it may not contain generator expressions.
- $<INSTALL_INTERFACE:...> = content of "..." when the property is exported using install(EXPORT), and empty otherwise.
- $<BUILD_INTERFACE:...> = content of "..." when the property is exported using export(), or when the target is used by another target in the same buildsystem. Expands to the empty string otherwise.
- $<PLATFORM_ID> = The CMake-id of the platform $<PLATFORM_ID:comp> = '1' if the The CMake-id of the platform matches comp, otherwise '0'.
- $<C_COMPILER_ID> = The CMake-id of the C compiler used.
- $<C_COMPILER_ID:comp> = '1' if the CMake-id of the C compiler matches comp, otherwise '0'.
- $<CXX_COMPILER_ID> = The CMake-id of the CXX compiler used.
- $<CXX_COMPILER_ID:comp> = '1' if the CMake-id of the CXX compiler matches comp, otherwise '0'.
- $<VERSION_GREATER:v1,v2> = '1' if v1 is a version greater than v2, else '0'.
- $<VERSION_LESS:v1,v2> = '1' if v1 is a version less than v2, else '0'.
- $<VERSION_EQUAL:v1,v2> = '1' if v1 is the same version as v2, else '0'.
- $<C_COMPILER_VERSION> = The version of the C compiler used.
- $<C_COMPILER_VERSION:ver> = '1' if the version of the C compiler matches ver, otherwise '0'.
- $<CXX_COMPILER_VERSION> = The version of the CXX compiler used.
- $<CXX_COMPILER_VERSION:ver> = '1' if the version of the CXX compiler matches ver, otherwise '0'.
- $<TARGET_FILE:tgt> = main file (.exe, .so.1.2, .a)
- $<TARGET_LINKER_FILE:tgt> = file used to link (.a, .lib, .so)
- $<TARGET_SONAME_FILE:tgt> = file with soname (.so.3)
-
-where "tgt" is the name of a target. Target file expressions produce
-a full path, but _DIR and _NAME versions can produce the directory and
-file name components:
-
-::
-
- $<TARGET_FILE_DIR:tgt>/$<TARGET_FILE_NAME:tgt>
- $<TARGET_LINKER_FILE_DIR:tgt>/$<TARGET_LINKER_FILE_NAME:tgt>
- $<TARGET_SONAME_FILE_DIR:tgt>/$<TARGET_SONAME_FILE_NAME:tgt>
-
-
-
-::
-
- $<TARGET_PROPERTY:tgt,prop> = The value of the property prop on the target tgt.
-
-Note that tgt is not added as a dependency of the target this
-expression is evaluated on.
-
-::
-
- $<TARGET_POLICY:pol> = '1' if the policy was NEW when the 'head' target was created, else '0'. If the policy was not set, the warning message for the policy will be emitted. This generator expression only works for a subset of policies.
- $<INSTALL_PREFIX> = Content of the install prefix when the target is exported via INSTALL(EXPORT) and empty otherwise.
-
-Boolean expressions:
-
-::
-
- $<AND:?[,?]...> = '1' if all '?' are '1', else '0'
- $<OR:?[,?]...> = '0' if all '?' are '0', else '1'
- $<NOT:?> = '0' if '?' is '1', else '1'
-
-where '?' is always either '0' or '1'.
-
-Expressions with an implicit 'this' target:
-
-::
-
- $<TARGET_PROPERTY:prop> = The value of the property prop on the target on which the generator expression is evaluated.
+Contents of COMPILE_DEFINITIONS may use "generator expressions" with the
+syntax "$<...>". See the :manual:`cmake-generator-expressions(7)` manual
+for available expressions.
.. include:: /include/COMPILE_DEFINITIONS_DISCLAIMER.txt