Refactoring #2275
Refactor cmake machinery for consistent Python interpreter/libraries handling
| Status: | Resolved | Start date: | 09 Jan 2019 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | pospelov | % Done: | 0% | |
| Category: | - | |||
| Target version: | Sprint 43 |
Description
Our long standing problem is inconsistency in Python interpreter and Python library versions. Even on Linux cmake often finds Python libraries which doesn't match Python interpreter.
We solve this problem by running our own ValidatePythonInstallation.cmake.
Seems that modern versions of CMake offers a module which takes care about consistency.
https://cmake.org/cmake/help/git-stage/module/FindPython.html
Within this item, investigate if we can switch to FindPython module. Questions to address:
Which will be the minimum CMake version requirement
How it works under Mac which is known for its messy Python-as-Framework-bundle.
How it works under Python virtual environment.
History
#1 Updated by pospelov over 1 year ago
- Status changed from Backlog to Sprint
- Target version set to Sprint 41
#2 Updated by pospelov about 1 year ago
- Target version changed from Sprint 41 to v2.0
Will be possible with cmake-1.12.
Scheduling for version 2.0.
#3 Updated by pospelov about 1 year ago
- Status changed from Sprint to Backlog
- Target version deleted (
v2.0)