File: CMP0202.rst

package info (click to toggle)
cmake 4.2.1-2
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 152,344 kB
  • sloc: ansic: 403,894; cpp: 303,807; sh: 4,097; python: 3,582; yacc: 3,106; lex: 1,279; f90: 538; asm: 471; lisp: 375; cs: 270; java: 266; fortran: 239; objc: 215; perl: 213; xml: 198; makefile: 108; javascript: 83; pascal: 63; tcl: 55; php: 25; ruby: 22
file content (30 lines) | stat: -rw-r--r-- 1,213 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
CMP0202
-------

.. versionadded:: 4.2

PDB file names always include their target's per-config POSTFIX.

Program database files (``.pdb``) are always named with their target's
:prop_tgt:`DEBUG_POSTFIX` or :prop_tgt:`<CONFIG>_POSTFIX` target property
value.

If the :prop_tgt:`PDB_NAME` target property is defined, CMake 4.1 and below
exclude the target's per-config postfix from the program data base file name.
Otherwise, the per-config postfix is included.  This is inconsistent.
CMake 4.2 and above prefer to always name the program database file with the
per-config postfix regardless how the name is computed, i.e., using
:prop_tgt:`OUTPUT_NAME`, or :prop_tgt:`PDB_NAME`, or neither.  This policy
provides compatibility with projects that have not been updated to account
for the new behavior.

The ``OLD`` behavior for this policy does not use the per-config postfix in
``.pdb`` file names if the :prop_tgt:`PDB_NAME` target property is defined.
The ``NEW`` behavior always uses the per-config postfix in ``.pdb`` file
names.

.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 4.2
.. |WARNS_OR_DOES_NOT_WARN| replace:: does *not* warn
.. include:: include/STANDARD_ADVICE.rst

.. include:: include/DEPRECATED.rst