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

Itś a bit ugle (and there is probably a combination of options that achieves the same effect), but the following checks only the dependencies of foo, not bar, but does recognise bar as a dependency of foo:

ROS_PACKAGE_PATH=`pwd`/src:$ROS_PACKAGE_PATH \
  rosdep check -i foo

At least on my system.

Itś a bit ugle (and there is probably a combination of options that achieves the same effect), but the following checks only the dependencies of foo, not bar, but does recognise bar as a dependency of foo:

ROS_PACKAGE_PATH=`pwd`/src:$ROS_PACKAGE_PATH \
  rosdep check -i foo

At least on my system.

None of the dependencies of bar will be checked in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.

Itś a bit ugle ugly (and there is probably a combination of options that achieves the same effect), but the following checks only the dependencies of foo, not bar, but does recognise bar as a dependency of foo:

ROS_PACKAGE_PATH=`pwd`/src:$ROS_PACKAGE_PATH \
  rosdep check -i foo

At least on my system.

None of the dependencies of bar will be checked in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.

Itś It's a bit ugly (and there is probably a combination of options that achieves the same effect), but the following checks only the dependencies of foo, not bar, but does recognise bar as a dependency of foo:

ROS_PACKAGE_PATH=`pwd`/src:$ROS_PACKAGE_PATH \
  rosdep check -i foo

At least on my system.

None of the dependencies of bar will be checked in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.

It's a bit ugly (and there is probably a combination of options that achieves the same effect), but the following checks only the dependencies of foo, not bar, but does recognise bar as a dependency of foo:

ROS_PACKAGE_PATH=`pwd`/src:$ROS_PACKAGE_PATH ROS_PACKAGE_PATH=/tmp/foobar_catkin_ws.Nxg25I/src:$ROS_PACKAGE_PATH \
  rosdep check -i foo

At least on my system.

None of the dependencies of bar will be checked in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.