ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You can try setting the COLCON_PYTHON_EXECUTABLE
explicitly to the location of the python
executable.
It's most likely that your python installation differs from the one used on our build farm to produce the binary for Windows. This is a common issue for platforms which have "rolling" dependency versions, i.e. when the default python install changes locations or versions our binary breaks.
Ultimately, building ROS 2 from source (https://index.ros.org/doc/ros2/Windows-Development-Setup/) on Windows and macOS is going to be more reliable (though not 100%).