# something obvious is missing, but we can't ask rosdep to 'install' # the following is somewhat optional: I like to run this to see if Rosinstall_generator -deps -tar -rosdistro=kinetic ros_base > ros_base.rosinstall # seed the workspace with a 'ros_base' set of packages Pip3 install -U rosdep rosinstall_generator wstool rosinstall # just the standard build-ros-from-source dependencies Pip3 install wheel empy defusedxml netifaces # these modules are needed but are not automatically installed In any case, as follows: # create a place for our Python3-ROS-Kinetic to liveĪpt install python3-venv libpython3-dev python-catkin-tools as such, this is not an answer to the general problem of how to build all of ROS 1 with Python 3 support.For many use-cases this is already quite sufficient though. No Open CV or other 'complex' packages/nodes. this only builds a bare-bones ROS Kinetic with Python 3.I always use a virtual environment, as it's typically the case that besides ROS, there are Python modules that need to be installed one might not want to "pollute" the system with. ROS Kinetic is already installed on that system (the.This is a more copy-pastable version of answer (but was too long for a comment). This will likely become obsolete with the release of Noetic, but as I've just had to build a version of Kinetic with Python 3 support (for the Nth time), I figured I'd post the commands I've used here (for myself as well).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |