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.
If a ROS message
my_pkg_1/MyMsg1depends on a messagemy_pkg_2/MyMsg2from another package and the typekit for the first package is generated usingros_generate_rtt_typekit(my_pkg_1), then, when attempting to use use this type in Orocos, this results in a compilation error due to theboost::serialization::serialize()function formy_pkg_2/MyMsg2not 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 callinginclude(${${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.