Skip to content
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.

Where to store messages and services #11

Open
anijjar opened this issue Jul 1, 2020 · 0 comments
Open

Where to store messages and services #11

anijjar opened this issue Jul 1, 2020 · 0 comments
Labels
documentation Improvements or additions to documentation wontfix This will not be worked on

Comments

@anijjar
Copy link
Member

anijjar commented Jul 1, 2020

After loosing much of my hair, I learned that the best way to create messages and services is to have a dedicated package for them. I call it, auvic_msgs. When every package has their own custom messages and services and if they are called by nodes contained in different packages, catkin_make will not take any action to build them first. Instead it will throw errors since the header files were not generated.

She you want to make a custom message or service. Put it in the auvic_msgs package.

Format: __name.srv/msg

@anijjar anijjar added documentation Improvements or additions to documentation wontfix This will not be worked on labels Jul 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant