-
Notifications
You must be signed in to change notification settings - Fork 118
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
More specific prefix in some cmake_parse_argument calls #523
More specific prefix in some cmake_parse_argument calls #523
Conversation
Signed-off-by: Kevin Egger <kevin.egger@sevensense.ch>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with green CI
CI (repos file build: |
I think the test failures on aarch64 are unrelated, but I'll have to wait to merge this PR until after the freeze: https://discourse.ros.org/t/freeze-of-ros-2-base-packages-upcoming-branch-and-tutorial-party-for-jazzy-jalisco/37191/2 |
Yes, they are unrelated. Going ahead and merging this one in. |
@Mergifyio backport iron humble jazzy |
✅ Backports have been created
|
Signed-off-by: Kevin Egger <kevin.egger@sevensense.ch> (cherry picked from commit fdbf457)
Signed-off-by: Kevin Egger <kevin.egger@sevensense.ch> (cherry picked from commit fdbf457)
Signed-off-by: Kevin Egger <kevin.egger@sevensense.ch> (cherry picked from commit fdbf457)
The macro
ament_auto_package
doesn't properly pass on the additional arguments toament_package
. The reason is that the call to the macroament_execute_extensions
again callscmake_parse_arguments
with the same variable prefix, effectively overwriting the original_ARG_UNPARSED_ARGUMENTS
variable and leaving it empty.I have found this issue to be present both in galactic (which I'm aware is already EOL) and rolling.
As a fix, I renamed changed the prefix argument for
cmake_parse_arguments
to have unique and non-conflicting variable names in both these macros.