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

Fix includes #18

Closed
wants to merge 1 commit into from
Closed

Fix includes #18

wants to merge 1 commit into from

Conversation

esteve
Copy link
Member

@esteve esteve commented Feb 4, 2016

No description provided.

@esteve esteve self-assigned this Feb 4, 2016
@esteve esteve added in progress Actively being worked on (Kanban column) in review Waiting for review (Kanban column) and removed in progress Actively being worked on (Kanban column) labels Feb 4, 2016
@esteve
Copy link
Member Author

esteve commented Feb 4, 2016

@jacquelinekay @wjwwood I had to make this change so rclpy would compile fine. Is this correct?

@esteve
Copy link
Member Author

esteve commented Feb 4, 2016

@jacquelinekay
Copy link
Contributor

I don't think including the message_type_support_struct.h header directly is necessary, but I'm really not sure. Waiting for William to weigh in here.

@esteve
Copy link
Member Author

esteve commented Feb 4, 2016

rcl and rclpy only need the typesupport structure, which is vendor independent, right? Neither rcl or rclpy need the ROSIDL_GET_MSG_TYPE_SUPPORT macros.

@wjwwood
Copy link
Member

wjwwood commented Feb 4, 2016

I'm pretty sure this is not the right thing to do, but instead I think what ever code is including these headers needs to also have include directories from exactly one type support system. That header (#include "rosidl_generator_c/message_type_support.h") is provided by each type support system and these rcl header files all include it so that anyone who tries to use these headers gets tied to a particular type support system when they do.

@wjwwood
Copy link
Member

wjwwood commented Feb 4, 2016

It's possible that your use case needs us to do something different, but what I mean to say is that these headers are intentionally the way they are.

@esteve
Copy link
Member Author

esteve commented Feb 4, 2016

@wjwwood no problem, I made this change so I could continue working on rclpy, but if the solution is somewhere else, that's fine too. I'm still getting up to speed with the new type support refactor 😄

@esteve
Copy link
Member Author

esteve commented Feb 4, 2016

I'm going to withdraw this PR and create an rclpy extension for each implementation. Thanks @jacquelinekay and @wjwwood for helping me understand the type support system.

@esteve esteve closed this Feb 4, 2016
@esteve esteve deleted the fix-typesupport-includes branch February 4, 2016 22:30
@esteve esteve removed the in review Waiting for review (Kanban column) label Feb 4, 2016
emersonknapp pushed a commit to aws-ros-dev/rcl that referenced this pull request Jun 3, 2019
ivanpauno pushed a commit that referenced this pull request Jan 2, 2020
changes to support proper life cycle of rmw objects
mauropasse pushed a commit to mauropasse/rcl that referenced this pull request Mar 31, 2021
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.

3 participants