You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The FindPythonInterp and FindPythonLibs modules are removed.
These modules have been deprecated since CMake 3.12.
CMake 3.27 and above prefer to not provide the modules. This policy provides
compatibility for projects that have not been ported away from them.
Projects using the FindPythonInterp and/or FindPythonLibs modules should
be updated to use one of their replacements:
FindPython3
FindPython2
FindPython
Both the Interpreter and Development checks called find_package(Python3
COMPONENTS Interpreter Development REQUIRED) independently. Combine
into a single call since find_package(Python3) should request all
needed components at once to ensure version consistency.
The old bridging code set Python3_ hints from PYTHON_ variables that
are no longer populated after the FindPython3 migration. The VTK8
path was also passing Python3_EXECUTABLE under the wrong variable name.
Fix by using find_package(Python3) results directly:
- VTK8 path: pass Python3_EXECUTABLE, Python3_INCLUDE_DIRS, and the
extracted PYTHON_LIBRARY under the old PYTHON_ variable names
- VTK9 path: pass the same values under Python3_ hint names
The superbuild export was missing Python3_INCLUDE_DIRS, Python3_LIBRARIES,
and PYTHON_EXECUTABLE. Add the modern Python3_ variables so downstream
superbuild projects using FindPython3 receive them, and re-add
PYTHON_EXECUTABLE for legacy project compatibility.
The default FindPython3 strategy (VERSION) searches all locations and
picks the newest Python3, which can find the wrong Python in
multi-version environments or when a virtualenv is active. Set
LOCATION strategy to stop at the first version found, respecting
PATH order and virtual environments.
0 commit comments