-
Notifications
You must be signed in to change notification settings - Fork 11
Generated header guards collide #30
Comments
Can you please report the bug upstream. |
This is not necessarily a bug upstream. |
It is certainly a bug upstream. Both types have the same name but different namespaces which distinguishes them. The header guard must include the namespaces. We could workaround the problem in post processing but would rather see this fixed upstream. |
Any fix for this? I'm struggling with the same problem |
This issues seems to be resolved 👍 |
Not resolved, but |
Reopening since the problem hasn't been resolved yet. |
@ipa-mdl Is the problem still present when using the latest OpenSplice release? When I try to build the control_msgs with the latest OpenSplice release I do not see any problems. |
It is still present if I install |
@ipa-mdl Which version of rosidl_typesupport_opensplice are you using? It should have be resolved in dashing. |
@MarcelJordense: the latest release: I will try to come up with a Travis build |
@MarcelJordense: Travis confirms that it works. I will close this issue :) |
control_msgs contains a
GripperCommand
action, which uses theGripperCommand
msg.For ROS2 dashing, this package (released version, 0.7.0, and master) generates C header files with duplicated guard names, e.g.
For this reason the build fails with:
Furthermore,
JointTrajectory.action
(control_msgs) collides withJointTrajectory.msg
(trajectory_msgs), both use_JOINTTRAJECTORY__H_
.For ROS2 crystal the generated header guards are less likely to collide, because goal, feedback and result are generated separately. (before #11?)
To avoid this problem the guards should contain the package name and the type to make them unique.
The files in
dds_opensplice
get generated byidlpp
though.The text was updated successfully, but these errors were encountered: