-
Notifications
You must be signed in to change notification settings - Fork 109
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
Modern CMake Targets #216
Comments
Yes, the goal is definitely to have Anyway, if you have some ideas on how to make this nicer, we'd be happy to consider them. |
There is a variable with all the CMake targets: |
Well I mean the approach that was taken seems like a first improvement. The PR for this was #178 (comment). Which also mentions a few issues, but seems like they all were resolved. For my own library I use similar code currently. But yeah in general the ideal solution would be to have a method in ros which does all the heavy work. Or if the existing methods like |
This duplicates ros2/rosidl#746. |
I would appreciate modern cmake targets, so things like
ament_target_dependencies
don't have to be used anymore (see ament/ament_cmake#292). It seems modern cmake targets are produced already by many interfaces such as std_msgs. For instance:std_msgs::std_msgs__rosidl_typesupport_cpp
But I saw some interfaces define a nicer wrapper library for this: For instance https://github.com/ros2/common_interfaces/blob/rolling/sensor_msgs/CMakeLists.txt#L67 (Although an alias target should be added as well for this).
So I wonder what the general strategy is. It seems a little bit inconsistent. I personally don't like these generated names such as
std_msgs::std_msgs__rosidl_typesupport_cpp
. So I would be in favor of having wrapper targets. On the other hand, it seems like this could be implemented directly inrosidl_generate_interfaces
and similar functions?The text was updated successfully, but these errors were encountered: