ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I have created another robot's description packages without those packages and it works perfectly.
it may have worked, but that package does not state the runtime dependency explicitly (at least for rviz
and xacro
).
For a regular desktop
or desktop-full
installation that will not typically result in any problems, as you'll have those already installed.
But anyone who installed ROS from source, or used any of the "bare bones" installation types (ie: ros-core
or ros-base
), they could run into problems, as even after running rosdep check --from-paths .. --ignore-src ..
(ie: the command that will make sure all dependencies of the ROS packages in a workspace are present on the system), they may not have RViz, nor xacro
.
2 | No.2 Revision |
Is it required to add the packages urdf, rviz and xacro?
The reason you add those package names to the catkin_create_pkg
invocation is to add those as run and (in this case: build) dependencies to the package manifest. We do that so that package managers and tools like rosdep
and catkin
can understand what your package needs in order to work correctly -- or at all.
I have created another robot's description packages without those packages and it works perfectly.
it may have worked, but that package does not state the runtime dependency explicitly (at least for rviz
and xacro
).
For a regular desktop
or desktop-full
installation that will not typically result in any problems, as you'll have those already installed.
But anyone who installed ROS from source, or used any of the "bare bones" installation types (ie: ros-core
or ros-base
), they could run into problems, as even after running rosdep check --from-paths .. --ignore-src ..
(ie: the command that will make sure all dependencies of the ROS packages in a workspace are present on the system), they may not have RViz, nor xacro
.