mirror of
https://github.com/Kitware/CMake.git
synced 2026-02-09 00:29:55 -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.
29 lines
1.0 KiB
ReStructuredText
29 lines
1.0 KiB
ReStructuredText
CMP0002
|
|
-------
|
|
|
|
Logical target names must be globally unique.
|
|
|
|
Targets names created with :command:`add_executable`, :command:`add_library`, or
|
|
:command:`add_custom_target` are logical build target names. Logical target
|
|
names must be globally unique because:
|
|
|
|
::
|
|
|
|
- Unique names may be referenced unambiguously both in CMake
|
|
code and on make tool command lines.
|
|
- Logical names are used by Xcode and VS IDE generators
|
|
to produce meaningful project names for the targets.
|
|
|
|
The logical name of executable and library targets does not have to
|
|
correspond to the physical file names built. Consider using the
|
|
:prop_tgt:`OUTPUT_NAME` target property to create two targets with the same
|
|
physical name while keeping logical names distinct. Custom targets
|
|
must simply have globally unique names (unless one uses the global
|
|
property :prop_gbl:`ALLOW_DUPLICATE_CUSTOM_TARGETS` with a Makefiles generator).
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 2.6.0
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: warns
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|