The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
And in fact, I could find the kobuki_msgs... Why aren't they part anymore of the full desktop install?
kobuki_msgs have never been part of any of the official ROS metapackages (neither any of the other kobuki_* packages). See REP-142.
| | 2 | No.2 Revision |
And in fact, I could find the kobuki_msgs... Why aren't they part anymore of the full desktop install?
kobuki_msgs have never been part of any of the official ROS metapackages (neither any of the other kobuki_* packages). See REP-142.
From your issue on the ros_moving_object tracker I gather that you've cloned the kobuki_msgs from source and added them to your workspace.
I would recommend you follow the workflow shown in #q252478 whenever you try to build something from sources in ROS. rosdep is the tool that installs dependencies of packages for you, and in this case would have installed the binary kobuki_msgs package for you, as it is actually released for ROS Kinetic.
| | 3 | No.3 Revision |
And in fact, I could find the kobuki_msgs... Why aren't they part anymore of the full desktop install?
kobuki_msgs have has never been part of any of the official ROS metapackages (neither any of the other kobuki_* packages). See REP-142.
From your issue on the ros_moving_object tracker I gather that you've cloned the kobuki_msgs from source and added them to your workspace.
I would recommend you follow the workflow shown in #q252478 whenever you try to build something from sources in ROS. rosdep is the tool that installs dependencies of packages for you, and in this case would have installed the binary kobuki_msgs package for you, as it is actually released for ROS Kinetic.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
