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

Add rclcpp and rclcpp_components dependencies to package.xml. (#569) #570

Merged
merged 1 commit into from Jul 29, 2020

Conversation

JWhitleyWork
Copy link
Collaborator

Forward-port of #569 to Foxy.

I noticed that these are listed in CMakeLists.txt but not in package.xml
and this is causing a build failure for the binary releases on
build.ros2.org:

http://build.ros2.org/view/Dbin_ubhf_uBhf/job/Dbin_uB64__depth_image_proc__ubuntu_bionic_amd64__binary/

Signed-off-by: Steven! Ragnarök <steven@nuclearsandwich.com>
@JWhitleyWork
Copy link
Collaborator Author

@nuclearsandwich Can I get a quick review?

@JWhitleyWork
Copy link
Collaborator Author

The build farm "failures" are due to warnings about deprecated CMake commands. However, I'll be updating all CMake files in this repo to use ament_auto which will fix any such issues so please ignore those failures for now.

@JWhitleyWork
Copy link
Collaborator Author

Thanks!

@JWhitleyWork JWhitleyWork merged commit 008b75e into ros2 Jul 29, 2020
@JWhitleyWork JWhitleyWork deleted the forward-ports/569 branch July 29, 2020 21:08
@nuclearsandwich
Copy link
Contributor

Forward-port of #569 to Foxy.

Sorry, I should have checked whether this was an issue on mainline distros. For my future edification am I correct that targeting the mainline and then backporting is preferred to targeting a stable distribution and forward-porting?

@JWhitleyWork
Copy link
Collaborator Author

@nuclearsandwich Yeah, generally. No big deal, though. I'm working on a big overhal of the CMakeLists.txt and package.xml files in this distro. When I'm done, would you mind reviewing it? Maintainership is getting a bit thin on this repo (no future responsibility implied with the review of this PR).

@nuclearsandwich
Copy link
Contributor

When I'm done, would you mind reviewing it

With the disclaimer that I'm rather overwhelmed by notifications, I will do my best to do so once tagged.

@JWhitleyWork
Copy link
Collaborator Author

Totally understand. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants