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.

Sign up for GitHub

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

Jump to bottom

Rosdep discovery of non-ament packages in a source workspace #157

Open
stonier opened this issue Dec 22, 2020 · 1 comment
Open

Rosdep discovery of non-ament packages in a source workspace #157

stonier opened this issue Dec 22, 2020 · 1 comment

Comments

@stonier
Copy link
Collaborator

stonier commented Dec 22, 2020 •
edited
Loading

Related to #139

Colcon can handle dependency discovery for non-ament packages (no `package.xml) when it computes the graph of packages to be built in the workspace. However, rosdep is blind to these when they reside in a source workspace.

Case in point, pybind11 is discovered by colcon, but not by rosdep.

maliput_py: Cannot locate rosdep definition for [pybind11]

I wonder if something could be done to improve rosdep in this regard?
@stonier
Copy link
Collaborator Author

stonier commented Dec 22, 2020

Likely very awkward - rosdep would have to start being build system aware, but for a working build environment, you need both dependency AND build tools working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stonier