Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rtt_roscomm: There is no dependency handling when generating typekits #173

Open
danieto98 opened this issue Jun 12, 2024 · 0 comments · May be fixed by #174
Open

rtt_roscomm: There is no dependency handling when generating typekits #173

danieto98 opened this issue Jun 12, 2024 · 0 comments · May be fixed by #174

Comments

@danieto98
Copy link

If a ROS message my_pkg_1/MyMsg1 depends on a message my_pkg_2/MyMsg2 from another package and the typekit for the first package is generated using ros_generate_rtt_typekit(my_pkg_1), then, when attempting to use use this type in Orocos, this results in a compilation error due to the boost::serialization::serialize() function for my_pkg_2/MyMsg2 not being defined.

It would be nice if typekits could also be generated automatically for these types of dependencies, to avoid having to hunt down and list every single dependency recursively in order to have complex ROS messages work.

I found a workaround by generating typekits for all dependencies listed in ${${my_pkg_1}_MSG_DEPENDENCIES}, which is set by calling include(${${my_pkg_1}_PREFIX}/${CATKIN_GLOBAL_SHARE_DESTINATION}/${my_pkg_1}/cmake/${my_pkg_1}-msg-paths.cmake). I believe something similar could be done.

@danieto98 danieto98 linked a pull request Jun 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant