ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I'm not sure what the cause is yet, but the following works for me (ie: rosdep
identifies the missing dependency correctly) with a ROS 1 workspace (ie: with Catkin packages) built by Colcon (in a ros:melodic
container):
rosdep check --from-paths /path/to/catkin_ws/install/share --ignore-src --rosdistro=melodic
Note the share/
in the argument to --from-paths
.
Without that, rosdep
for some reason doesn't identify the missing dependency.
It does discover my test package though, so I'm not sure what's going on there.
Running with --verbose
gives me:
resolving for resources [test_pkg]
when adding the share/
, but:
resolving for resources []
without share/
.
It's likely there is already an issue on ros-infrastructure/rosdep
about this, but I haven't found it (yet).
2 | No.2 Revision |
I'm not sure what the cause is yet, but the following works for me (ie: rosdep
identifies the missing dependency correctly) with a ROS 1 workspace (ie: with Catkin packages) built by Colcon (in a ros:melodic
container):
rosdep check --from-paths /path/to/catkin_ws/install/share --ignore-src --rosdistro=melodic
Note the share/
in the argument to --from-paths
.
Without that, rosdep
for some reason doesn't identify the missing dependency.
It does discover my test package though, so I'm not sure what's going on there.
Running with --verbose
gives me:
resolving for resources [test_pkg]
when adding the share/
, but:
resolving for resources []
without share/
.
It's likely there is already an issue on ros-infrastructure/rosdep
about this, but I haven't found it (yet).
Note: this is with --merge-install
. I expect you'd have to list the paths to all share/
subdirs of all the pkgs in your workspace (ie: install/$pkg/share
) otherwise.
3 | No.3 Revision |
I'm not sure what the cause is yet, but the following works for me (ie: rosdep
identifies the missing dependency correctly) with a ROS 1 workspace (ie: with Catkin packages) built by Colcon (in a ros:melodic
container):
rosdep check --from-paths /path/to/catkin_ws/install/share --ignore-src --rosdistro=melodic
Note the share/
in the argument to --from-paths
.
Without that, rosdep
for some reason doesn't identify the missing dependency.
It does discover my test package though, so I'm not sure what's going on there.
Running with --verbose
gives me:
resolving for resources [test_pkg]
when adding the share/
, but:
resolving for resources []
without share/
.
It's likely there is already an issue on ros-infrastructure/rosdep
about this, but I haven't found it (yet).(yet) (edit: could actually be ros-infrastructure/rosdep#724).
Note: this is with --merge-install
. I expect you'd have to list the paths to all share/
subdirs of all the pkgs in your workspace (ie: install/$pkg/share
) otherwise.
4 | No.4 Revision |
I'm not sure what the cause is yet, but the following works for me (ie: rosdep
identifies the missing dependency correctly) with a ROS 1 workspace (ie: with Catkin packages) built by Colcon (in a ros:melodic
container):
rosdep check --from-paths /path/to/catkin_ws/install/share --ignore-src --rosdistro=melodic
Note the share/
in the argument to --from-paths
.
Without that, rosdep
for some reason doesn't identify the missing dependency.
It does discover my test package though, so I'm not sure what's going on there.
Running with --verbose
gives me:
resolving for resources [test_pkg]
when adding the share/
, but:
resolving for resources []
without share/
.
It's likely there is already an issue on ros-infrastructure/rosdep
about this, but I haven't found it (yet) (edit: could actually be ros-infrastructure/rosdep#724).
Note: this is with --merge-install
. I expect you'd have to list the paths to all share/
subdirs of all the pkgs in your workspace (ie: install/$pkg/share
) otherwise.
Edit: this probably has something to do with rosdep
only looking at the Ament Index when parsing workspaces built by Colcon, and only looking for files under share/
(and failing if they're not where it expects them to be), instead of crawling the hierarchy below catkin_ws/install
.