ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Building some ros packages from source code can be a bit of a challenge. For historical reasons, there are two build systems: catkin_make and "catkin build". They are not compatible.

Secondly, it's very questionable that the catkin_virtualenv package is trying to use python2 in noetic. It's Readme indicates it wants to be built with "catkin build". It is probably better to build that in its own catkin_ws and install it to /opt/ros rather than having that source package in your local ~/catkin_ws/src/ directory.

You got unlucky that this driver just isn't a good package for a beginner to learn how to build a ros package. It's not usually so difficult.

Building some ros packages from source code can be a bit of a challenge. For historical reasons, there are two build systems: catkin_make and "catkin build". They are not compatible.

Secondly, it's very questionable that the catkin_virtualenv package is trying to use python2 in noetic. It's Readme indicates it wants to be built with "catkin build". It is probably better to build that in its own catkin_ws and install it to /opt/ros rather than having that source package in your local ~/catkin_ws/src/ directory.

You got unlucky that this driver just isn't a good package for a beginner to learn how to build a ros package. For most ros packages, It's not usually so difficult.

Building some ros packages from source code can be a bit of a challenge. For historical reasons, there are two build systems: catkin_make and "catkin build". They are not compatible.

Secondly, it's very questionable that the catkin_virtualenv package catkin_virtualenv doesn't look like it is trying to use python2 a ros package, so it doesn't go in noetic. you catkin_ws. It's Readme indicates it wants to be built with "catkin build". It is probably better to build that in its own catkin_ws and install it to /opt/ros rather than having that source package in your local ~/catkin_ws/src/ directory.a "system" python package

You got unlucky that this driver just isn't a good package for a beginner to learn how to build a ros package. For most ros packages, It's not so difficult.

Building some ros packages from source code can be a bit of a challenge. For historical reasons, there are two build systems: catkin_make and "catkin build". They are not compatible.

Secondly, catkin_virtualenv doesn't look like it is a ros package, so it doesn't go in you catkin_ws. your catkin_ws tree. It's a "system" python package

You got unlucky that this driver just isn't a good package for a beginner to learn how to build a ros package. For most ros packages, It's not so difficult.