You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm starting to think that the most commonly used types should be included in mros2_msgs/ (in this repository). This is because the generation of custom msg types is a common feature of mros2, not platform-dependent, and this way will make the usability higher.
The expected issue is that if users individually generate their own msg type files at their own locations, link conflict (duplication of include file) may happen.
We initially thought the location of files related to the msg type of mros2 should be as follows.
mros2
as a library, should contain onlystd_msgs
atmros2_msgs/
.However, there are some commonly used types, such as
geometry_msgs
andsensor_msgs
. Actually, sensor_msgs is now located at thismros2
repository: https://github.com/mROS-base/mros2/tree/main/mros2_msgs/sensor_msgs/msgSo we need to discuss again which location is suitable to manage these types.
The text was updated successfully, but these errors were encountered: