Open KTHARIKRISHNA opened 1 year ago
uint8 TL_COLOR_NOLIGHT = 0 # /*< \n /
So I bisected it down to (mostly) this line. My best guess is that the newline here is confusing the parser and making it so that it things the */
is the start of a newline. Removing that \n
makes it get by this particular error.
However, even if this is removed, the parser also doesn't like the /*
within the comments. That's because we take the message comments and embed them inside of comments in the generated code, so you end up with something like:
/**
* /**< compatible with AV2 protocol coding */
*/
And that confused the C++ parser.
The best advice I can give to you for now would be to remove the \n
and the /** .. */
parts from the comments. There is probably a bug to be fixed for the \n
problem, so I'll leave this open on the backlog to look into that.
Thanks for the explanation. Currently I am using this msg file without any comments in it right now. But May I know what is the change that is causing this issue in Humble. As I said, this is working correctly in Foxy. What is the upgrade that happened related to this parsing from Foxy to Humble?
But May I know what is the change that is causing this issue in Humble.
I'm not entirely sure. It may be the case that in Foxy, we didn't insert the comments from the .msg
file into the .hpp
files, so the issue just didn't arise.
Bug report
Required Info:
Steps to reproduce issue
In ROS 2 Humble, do colcon build for ROS 2 custom message with CaspEvent.msg as shown below:
CaspEvent.msg
Expected behavior
Build should be successful
Actual behavior
Build failed with the following error:
Additional information
Build was successful in ROS 2 Foxy but it is broken in Humble.
This is the complete build log: stdout_stderr.log