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
add dependency on ros-melodic-tf #10
Conversation
To allow bridging tf/tfMessage out of the box
The right approach for this is to add |
Edit: the package.xml is used to specify ROS2 dependencies. In this case we are missing some ROS1 package to be installed to generate mappings, so it has to be done in the control file instead of the package.xml |
@mjcarroll for a Dashing backport. |
@mjcarroll @nuclearsandwich friendly 🛎️ any chance of getting this in an upcoming release ? |
@jacobperron this may also be of interest for foxy |
To allow bridging tf/tfMessage out of the box
To allow bridging tf/tfMessage out of the box
To allow bridging tf/tfMessage out of the box
To allow bridging tf/tfMessage out of the box
To allow bridging tf/tfMessage out of the box
To allow bridging
tf/tfMessage
out of the box.The ROS 2 version of the package has the corresponding bridging rules https://github.com/ros2/geometry2/blob/6233bc6592ee34ce2c08760d0151a03471a44097/tf2_msgs/tfmessage_bridge_mapping_rule.yaml but the factories are not generated because the ROS1 package is not installed
(would benefit from a Dashing backport too)
Edit: would address issues like https://answers.ros.org/question/349088/ros1-tf-incompatible-with-ros2-through-ros1-bridge/ when installing from debs