CMP0201ΒΆ
Added in version 4.2.
The modules FindPython3, FindPython2 and
FindPython change the handling of the NumPy
component and, respectively, the definition of the Python3::NumPy,
Python2::NumPy and Python::NumPy targets.
For CMake 4.2 and above, the specification of the NumPy component does not
imply anymore the component Development.Module and the Python3::NumPy,
Python2::NumPy and Python::NumPy targets provided, respectively, by the
modules FindPython3, FindPython2 and FindPython
do not depend on the Python3::Development.Module,
Python2::Development.Module and Python::Development.Module targets.
For CMake 4.1 and below, the specification of the NumPy component imply the
component Development.Module and the Python3::NumPy, Python2::NumPy
and Python::NumPy targets provided, respectively, by the modules
FindPython3, FindPython2 and FindPython depend on
the Python3::Development.Module, Python2::Development.Module and
Python::Development.Module targets.
The OLD behavior for this policy creates a dependency of the NumPy
target over the Development.Module target. The NEW behavior does not
create a dependency of the NumPy target over the Development.Module
target.
This policy provides compatibility with projects that expect the legacy behavior.
This policy was introduced in CMake version 4.2.
It may be set by cmake_policy() or cmake_minimum_required().
If it is not set, CMake does not warn, and uses OLD behavior.
Note
The OLD behavior of a policy is
deprecated by definition
and may be removed in a future version of CMake.