summaryrefslogtreecommitdiff
path: root/share/cmake-3.5/Help/prop_sf/COMPILE_DEFINITIONS.rst
diff options
context:
space:
mode:
Diffstat (limited to 'share/cmake-3.5/Help/prop_sf/COMPILE_DEFINITIONS.rst')
-rwxr-xr-xshare/cmake-3.5/Help/prop_sf/COMPILE_DEFINITIONS.rst20
1 files changed, 20 insertions, 0 deletions
diff --git a/share/cmake-3.5/Help/prop_sf/COMPILE_DEFINITIONS.rst b/share/cmake-3.5/Help/prop_sf/COMPILE_DEFINITIONS.rst
new file mode 100755
index 0000000..7f7e7c7
--- /dev/null
+++ b/share/cmake-3.5/Help/prop_sf/COMPILE_DEFINITIONS.rst
@@ -0,0 +1,20 @@
+COMPILE_DEFINITIONS
+-------------------
+
+Preprocessor definitions for compiling a source file.
+
+The COMPILE_DEFINITIONS property may be set to a semicolon-separated
+list of preprocessor definitions using the syntax VAR or VAR=value.
+Function-style definitions are not supported. CMake will
+automatically escape the value correctly for the native build system
+(note that CMake language syntax may require escapes to specify some
+values). This property may be set on a per-configuration basis using
+the name COMPILE_DEFINITIONS_<CONFIG> where <CONFIG> is an upper-case
+name (ex. "COMPILE_DEFINITIONS_DEBUG").
+
+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). Xcode does not support
+per-configuration definitions on source files.
+
+.. include:: /include/COMPILE_DEFINITIONS_DISCLAIMER.txt