-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Build failed with latest ros2 rolling source builds #4816
Comments
A few updates were made before the holidays in TF -- we have an open PR for updating to resolve the API change here #4732. I retriggered CI to check if we're all building again and will merge once ready! Thanks for the report |
@chanhhoang99 are you building geometry2 rolling from source? I'm not seeing it in the binaries yet and there hasn't been a rolling release since the depreciation warnings were added. |
Hi @SteveMacenski , |
@chanhhoang99 we should have this resolved sometime this month for source builds, for now you could use the tagged version of rolling's geometry_msgs instead of the latest on the main branch ( We could also update Nav2's CI to have geometry2 built from source as well and merge this in, but that would break |
L.O.L. for me The rolling release just happened 20 hours ago. I kick started that PR job and likely should be able to merge this within an hour to resolve the problem 😆 |
Merged! Thanks for the report |
Bug report
Required Info:
Steps to reproduce issue
Expected behavior
Build should be passed
Actual behavior
Received failure log:
Additional information
There is change from upstream of ros2/tf2 headers, should we use -Wno-error=cpp to ignore this error ?
The text was updated successfully, but these errors were encountered: