Skip to content

Pull Request for adding scope keywords feature in rosidl_target_interfaces (Issue#400) #798

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

Closed
wants to merge 2 commits into from

Conversation

FahadRazaKhan
Copy link

This PR is for the issue#400 "Using rosidl_target_interfaces incompatible with keyword target_link_libraries command". As rosidl_target_interfaces did not have the scope keyword options it could become incompatible with the target_link_libraries command if used with a scope keyword.

@FahadRazaKhan
Copy link
Author

Do I need to sign-off my commit?

@FahadRazaKhan FahadRazaKhan reopened this Apr 5, 2024
@FahadRazaKhan FahadRazaKhan changed the title Pull Request for Issue#400 Pull Request for adding scope keywords feature in rosidl_target_interfaces (Issue#400) Apr 5, 2024
@clalancette
Copy link
Contributor

Do I need to sign-off my commit?

Yes.

Besides that, please remove other changes to this PR that don't directly have to do with the issue you are trying to fix. It makes it difficult to review and see what is actually being changed.

@FahadRazaKhan
Copy link
Author

@clalancette Thanks for the feedback. For the sign-off, should I rebase my branch or is it unsafe?
The other changes I did not incorporate, I believe these changes just appeared because of syncing with the latest branch.

@clalancette
Copy link
Contributor

@clalancette Thanks for the feedback. For the sign-off, should I rebase my branch or is it unsafe?

Yes, rebasing is fine.

The other changes I did not incorporate, I believe these changes just appeared because of syncing with the latest branch.

Yes. You'll need to make sure your change is "clean" on top of those, so we only see the differences you are trying to make. When you rebase to add the sign-off, you should also make sure this is the case.

…target_interfaces function. The feature is added for the better compatibility with the target_link_libraries command as requested in issue#400

Signed-off-by: Fahad <fahad.raza@desaysv.com>
@FahadRazaKhan FahadRazaKhan reopened this Apr 9, 2024
@FahadRazaKhan
Copy link
Author

@clalancette I have removed the other changes. Can you please review. Thanks.

Copy link
Contributor

@fujitatomoya fujitatomoya left a 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.

Note, can we add scope keywords are optionally supported in the doc section?

@FahadRazaKhan
Copy link
Author

lgtm with green CI.

Note, can we add scope keywords are optionally supported in the doc section?

Can you be more specific, sorry I did not get it.

@FahadRazaKhan
Copy link
Author

@clalancette and @fujitatomoya any update?

@fujitatomoya
Copy link
Contributor

Note, can we add scope keywords are optionally supported in the doc section?

im sorry, bad memory 😓 I think what i mean was to add an explanation in function doc header, line 22 -

Signed-off-by: Fahad <fahad.raza@desaysv.com>
@FahadRazaKhan
Copy link
Author

@fujitatomoya thank you for your explanation. I have added a few comments in the doc header as you suggested. Please have a review.

@FahadRazaKhan
Copy link
Author

@fujitatomoya just a reminder that I have updated the doc header.

@FahadRazaKhan
Copy link
Author

@clalancette Hi, it's been a month since I updated the PR. I believe @fujitatomoya is busy so can someone else review and approve it please?

Copy link
Contributor

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry for being late to get back.

lgtm, i would like to have another review.

@FahadRazaKhan
Copy link
Author

@fujitatomoya any update? are you asking someone else for another review?

@fujitatomoya
Copy link
Contributor

@clalancette @sloretz can you have a look when you have time?

@FahadRazaKhan
Copy link
Author

@clalancette @sloretz @fujitatomoya guys this is a long pending PR. Would you please give it a final review and accept for merge. Thanks.

@sloretz sloretz self-assigned this Jul 12, 2024
@sloretz
Copy link
Contributor

sloretz commented Jul 12, 2024

Thank you for the PR and patience @FahadRazaKhan . The bad news is I don't think we should take this PR because this method has been deprecated for three years. The good news is there's already a solution to the problem you described that you can use today.

Say you want to use C++ messages from the same package, and you have a line like this:

rosidl_target_interfaces(target_name ${PROJECT_NAME} "rosidl_typesupport_cpp")

Change it to this

  rosidl_get_typesupport_target(cpp_typesupport_target ${PROJECT_NAME} "rosidl_typesupport_cpp")
  target_link_libraries(target_name PRIVATE "${cpp_typesupport_target}")

See this PR for a real example: https://github.com/ros2/common_interfaces/pull/156/files

@sloretz sloretz closed this Jul 12, 2024
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.

4 participants