We have started looking into ROS2 and like many aspects. We had planned to rework some of our packages with a core software library and thin ROS wrapper (similar to nodelets/MoveIt/Tf) usage, but one issue that has been a stumbling block for us is that we use ROS messages as basic data types and prefer to pass const pointers for most of our data handling.
It seems that ROS2 uses the ROS1-style message generators, but the output headers are placed in different locations making it difficult to have common source files that can be built for either ROS1 or ROS2.
Is it possible to have a common header generation scheme so either ROS1 or ROS2 puts the headers and Python class files into a "common" location relative to the include paths based on package setups?
---
[Visit Topic](
https://discourse.ros.org/t/software-reuse-in-ros1-and-ros2/2262/6) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)