Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lpp rosdep workflow fails #17

Open
rikba opened this issue Aug 31, 2023 · 2 comments
Open

lpp rosdep workflow fails #17

rikba opened this issue Aug 31, 2023 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@rikba
Copy link

rikba commented Aug 31, 2023

I have lpp installed in my regular catkin workspace

catkin_ws
-- src
-- -- lpp
-- -- another package depending on lpp in package.xml

My problem is that I get the following error when trying to install the dependencies using rosdep

For example

rosdep install omav_hovery_core
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
omav_hovery_core: Cannot locate rosdep definition for [lpp]

My guess is there is some export or install missing in LPP's CMakeLists or I need to tell rosdep somehow to also look in the sources workspace to find dependencies. Thus rodep does not know that lpp is within catkin workspace. Do you know what to do @4c3y ?

@rikba rikba added enhancement New feature or request help wanted Extra attention is needed labels Aug 31, 2023
@4c3y
Copy link
Member

4c3y commented Nov 6, 2023

AFAIK rosdep is only designed to install system dependencies. It is not designed to install other ROS packages needed by omav_hovery_core

@pascalau
Copy link

rosdep can install both ROS packages as well as system dependencies. Which is which is defined in this repository which is queried when one runs rosdep update. The yaml files in this repository map entries in package.xml files to packages for the respective package managers on different OS's and distros. If a dependency is not listed there it will try to install it as a ros package (ros-$ROSDISTRO-package-name). Since lpp is already present in the workspace and should not be considered one can add the -i or --ignore-src flag which will prevent rosdep to install packages already present in the workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants