Open tony-p opened 1 year ago
We've had reports of this issue on both Linux and MacOS as well https://github.com/RoboStack/robostack.github.io/issues/27 (Linux; particular distributions only!) https://github.com/RoboStack/robostack.github.io/issues/35 MacOS (osx-arm64)
/cc @traversaro
On windows if using python 3.10. in the env and have python 3.11. installed globally, no matter what I do (disabling managed aliases etc) FindPython3.cmake will find/prefer the global Python 3.11 install over the environment installed python 3.10 which eventually leads to package version conflicts in builds.
The global Python3 is found even if you specify the Python3_EXECUTABLE
location via -DPython3_EXECUTABLE=
? Probably it may be worth to also try to set Python3_FIND_STRATEGY
to LOCATION
, see https://cmake.org/cmake/help/latest/module/FindPython3.html#hints . If you control the project you are building, making sure that policy CMP0094
is set to NEW
, could also help.
Solution to issue cannot be found in the documentation.
Issue
On windows if using python 3.10. in the env and have python 3.11. installed globally, no matter what I do (disabling managed aliases etc) FindPython3.cmake will find/prefer the global Python 3.11 install over the environment installed python 3.10 which eventually leads to package version conflicts in builds. The only thing that solves it is removing all global python installs.
Note I am using this within a pixi environment (https://prefix.dev/docs/pixi/overview) However I don't believe this would affect this behaviour
Installed packages
Environment info