mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-05 21:31:08 -06:00
ad3c2c0b03
Every policy's documentation has a paragraph on what version of CMake introduced it, how to set the policy, and whether CMake warns if the policy is not set. The wording of this paragraph has diverged across policies over time. Factor the paragraph out into a standard advice document included by every policy.
32 lines
1.3 KiB
ReStructuredText
32 lines
1.3 KiB
ReStructuredText
CMP0098
|
|
-------
|
|
|
|
.. versionadded:: 3.17
|
|
|
|
:module:`FindFLEX` runs ``flex`` in directory
|
|
:variable:`CMAKE_CURRENT_BINARY_DIR` when executing.
|
|
|
|
The module provides a ``FLEX_TARGET`` macro which generates FLEX output.
|
|
In CMake 3.16 and below the macro would generate a custom command that runs
|
|
``flex`` in the current source directory. CMake 3.17 and later prefer to
|
|
run it in the build directory and use :variable:`CMAKE_CURRENT_BINARY_DIR`
|
|
as the ``WORKING_DIRECTORY`` of its :command:`add_custom_command` invocation.
|
|
This ensures that any implicitly generated file is written relative to the
|
|
build tree rather than the source tree, unless the generated file is
|
|
provided as absolute path.
|
|
|
|
This policy provides compatibility for projects that have not been updated
|
|
to expect the new behavior.
|
|
|
|
The ``OLD`` behavior for this policy is for ``FLEX_TARGET`` to use
|
|
the current source directory for the ``WORKING_DIRECTORY`` and where
|
|
to generate implicit files. The ``NEW`` behavior of this policy is to
|
|
use the current binary directory for the ``WORKING_DIRECTORY`` relative to
|
|
which implicit files are generated unless provided as absolute path.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 3.17
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: does *not* warn
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|