Fix python bindings doc for compiling in conda env #1506
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.
As mentioned by @fspindle, current compilation tutorial for ViSP python bindings in a conda environment was generating some warning at the cmake configuration step, as some system libraries were used by the build chain. This was due to the lack of installation of all build tools packaged by conda to enforce conda environment isolation.
Users/developers must install all the build tools packaged by conda:
conda install cmake cxx-compiler make
(or replace
make
by any other build system of your choice).We may also want to switch the recommended build system for
ninja
on all plaftorms for more consistency (already used on Windows for ViSP conda package and planned to migrate for ubuntu/macOS as well).