ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Itś a bit ugle (and there is probably a combination of options that achieves the same effect), but the following check
s 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.
2 | No.2 Revision |
Itś a bit ugle (and there is probably a combination of options that achieves the same effect), but the following check
s 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 check
ed in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.
3 | No.3 Revision |
Itś a bit ugle ugly (and there is probably a combination of options that achieves the same effect), but the following check
s 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 check
ed in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.
4 | No.4 Revision |
Itś It's a bit ugly (and there is probably a combination of options that achieves the same effect), but the following check
s 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 check
ed in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.
5 | No.5 Revision |
It's a bit ugly (and there is probably a combination of options that achieves the same effect), but the following check
s 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 check
ed in this example. Normally that would result in a potentially non-building workspace, but I believe that is what you asked for.