Streamline configuration of client project adding PYTHON_* and Python3_* variables vtk-config (or alike)
To streamline the configuration of project that do not directly use python but depends on a VTK build tree wrapped in python, it would be helpful to include all the python variables in the VTK configuration associated with the build tree.
The goal is to avoid passing blocks like these ones and expect VTK to find the python it was build against:
-DPYTHON_EXECUTABLE:FILEPATH=${PYTHON_EXECUTABLE}
-DPYTHON_LIBRARY:FILEPATH=${PYTHON_LIBRARY}
-DPYTHON_INCLUDE_DIR:FILEPATH=${PYTHON_INCLUDE_DIR}
-DPython3_EXECUTABLE:FILEPATH=${Python3_EXECUTABLE}
-DPython3_LIBRARY:FILEPATH=${Python3_LIBRARY}
-DPython3_INCLUDE_DIR:PATH=${Python3_INCLUDE_DIR}
Notes:
- These comments only apply to a VTK build tree and NOT a VTK install tree.
References:
Edited by Jean-Christophe Fillion-Robin