Revision da6bb1621d23c634b117351440e59b9f6118d5eb authored by Brad King on 05 June 2023, 10:42:22 UTC, committed by Kitware Robot on 05 June 2023, 10:42:37 UTC
f4d28d9e27 HIP: Fix implicit include directory detection under /usr/include Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !8534
COMPILE_DEFINITIONS.rst
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. Xcode does not support per-configuration
definitions on source files.
.. versionadded:: 3.26
Any leading ``-D`` on an item will be removed.
.. include:: /include/COMPILE_DEFINITIONS_DISCLAIMER.txt
Contents of ``COMPILE_DEFINITIONS`` may use :manual:`cmake-generator-expressions(7)`
with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)`
manual for available expressions. However, :generator:`Xcode`
does not support per-config per-source settings, so expressions
that depend on the build configuration are not allowed with that
generator.
Generator expressions should be preferred instead of setting the alternative per-configuration
property.
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...