Revert installing Python module systemwide. #473
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lines
cause CMake to find the directory where Python modules are installed. This would be the systemwide directory if one is simply building with the systemwide Python. If one has a venv active it'll install into that virtual environment.
Note that
CMAKE_INSTALL_PREFIX
doesn't affect where the module will be installed. Therefore, this will cause build/installation failure.Installing into a venv is questionable, because that's the responsibility of the Python package manager. Which will do so correctly without the additional CMake
install
statement.Finally, even if the install succeeds, it only installs the
lib*.so
without any__init__.py
files. Therefore, it leads to a broken installation, e.g.will successfully import
morphio
but there won't be anymorphio.Soma
, because that's handled via__init__.py