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

ROS2 Support #38

Closed
myungjoo opened this issue Sep 13, 2020 · 3 comments · Fixed by #55, #56, #48, #49 or #50
Closed

ROS2 Support #38

myungjoo opened this issue Sep 13, 2020 · 3 comments · Fixed by #55, #56, #48, #49 or #50
Assignees

Comments

@myungjoo
Copy link
Member

myungjoo commented Sep 13, 2020

We have potential clients who are using ROS2 right now.
(I will have meeting tomorrow and fetch their requirements.)

@wooksong
Copy link
Member

@myungjoo How about branching out for ROS1?

  • ros1 or ros distro name (Melodic?)
  • main (for ros2)

@myungjoo
Copy link
Member Author

Let's not branch out for ROS1 and ROS2.
I'd rather recommend to modularize (e.g., with euphemism: ros-common.c, ros1.c, and ros2.c) or to add #if #endif with build options.

@wooksong
Copy link
Member

@myungjoo Got it. Since build scripts are not compatible with each other, the hierarchies of them would be complex to well organize them. But I understood what you meant.

@wooksong wooksong reopened this Nov 6, 2020
@wooksong wooksong pinned this issue Nov 6, 2020
@wooksong wooksong reopened this Nov 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment