Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For cases where users get the macros in the wrong order.
I assume it does not cause errors to call e.g. add_message_files twice.
The only problem case left is if the user forgets to call generate_messages(). I though about checking that in catkin_package(), but not sure whether that's a good idea.
I think the following could maybe be better: make the xyz_genfoo macros depend on a target xyz_generation_check, that is initialised with message(FATAL_ERROR "generate_messages not called").
And in generate_messages(), the target is then overwritten by No-op. What do you think?