mirror of
https://github.com/reactos/CMake.git
synced 2024-12-02 00:26:18 +00:00
352cbb6e36
When we explain in add_definitions documentation that it is intended only for preprocessor definitions, link to add_compile_options for adding other flags. Also explicitly mention that the order of add_definitions calls with respect to target creation does not matter. This differs from the behavior now explicitly stated in the documentation of add_compile_options.
28 lines
1.1 KiB
ReStructuredText
28 lines
1.1 KiB
ReStructuredText
add_definitions
|
|
---------------
|
|
|
|
Adds -D define flags to the compilation of source files.
|
|
|
|
::
|
|
|
|
add_definitions(-DFOO -DBAR ...)
|
|
|
|
Adds definitions to the compiler command line for targets in the current
|
|
directory and below (whether added before or after this command is invoked).
|
|
This command can be used to add any flags, but it is intended to add
|
|
preprocessor definitions (see the :command:`add_compile_options` command
|
|
to add other flags).
|
|
Flags beginning in -D or /D that look like preprocessor definitions are
|
|
automatically added to the :prop_dir:`COMPILE_DEFINITIONS` directory
|
|
property for the current directory. Definitions with non-trivial values
|
|
may be left in the set of flags instead of being converted for reasons of
|
|
backwards compatibility. See documentation of the
|
|
:prop_dir:`directory <COMPILE_DEFINITIONS>`,
|
|
:prop_tgt:`target <COMPILE_DEFINITIONS>`,
|
|
:prop_sf:`source file <COMPILE_DEFINITIONS>` ``COMPILE_DEFINITIONS``
|
|
properties for details on adding preprocessor definitions to specific
|
|
scopes and configurations.
|
|
|
|
See the :manual:`cmake-buildsystem(7)` manual for more on defining
|
|
buildsystem properties.
|