ros1_bridge
ros1_bridge copied to clipboard
ROS 2 package that provides bidirectional communication between ROS 1 and ROS 2
Follows [comment](https://github.com/ros2/ros1_bridge/issues/316#issuecomment-853571152) in #316 Signed-off-by: Servando German Serrano
## Bug report **Required Info:** - Operating System: - Ubuntu 18.04/20.04 - Installation type: - binaries for everything ros1_bridge - Version or commit hash: - dasing and foxing - DDS...
## Bug report **Required Info:** - Operating System: - Ubuntu 18.04 - Installation type: - Binaries - Version or commit hash: - eloquent: 60f903c - DDS implementation: - RTI Connext...
## Bug report **Required Info:** - Operating System: - Ubuntu 18.04, inside Docker - Installation type: - Based on ros:foxy-ros1-bridge:latest - Version or commit hash: - N/A - DDS implementation:...
## Bug report **Required Info:** - Operating System: Ubuntu 18.04 - - Installation type: Binary - - Version or commit hash: dashing - - DDS implementation: Default - - Client...
`iterate_packages` might return ROS2 paths for already found ROS1 pkgs This results in duplicated entries in `data` and double definitions in the generated cpp code. This happens to me building...
This PR introduces package whitelist resp. blacklist, see https://github.com/ros2/ros1_bridge/issues/284. If a file `${CMAKE_SOURCE_DIR}/../../../BridgePackageInclude.List"` is found and non-empty (one ROS package name per line), only those ROS packages are mapped by...
Allow to exclude certain message types and/or packages from the rosbridge build. This could be done at cmake time, e.g., through cmake configuration options. AFAIR, this can be helpful to:...
Updated rosbridge to handle services with rule-based name matching. Motivating use: ROS2 has more strict rules on variable name format in services than ROS1, requiring a name change between ROS1...