Section: robotpkg/middleware
Priority: extra
Maintainer: mallet@laas.fr
Source: /opt/robotpkg/var/lib/robotpkg/packages/bsd/Ubuntu-22.04-x86_64/pub/ros2-rmw-fastrtps-9.5.1.tgz
Package: robotpkg-ros2-rmw-fastrtps
Version: 9.5.1
Architecture: amd64
Homepage: https://github.com/rmw_fastrtps/
Depends: robotpkg-ros2-tracing (= 7.1.0), robotpkg-ros2-rosidl-dynamic-typesupport-fastrtps (= 0.1.0) | robotpkg-ros2-rosidl-dynamic-typesupport-fastrtps (= 0.6.0), robotpkg-ros2-rosidl-dynamic-typesupport (= 0.1.1), robotpkg-ros2-rosidl-buffer (= 5.3.1), robotpkg-ros2-rosidl (= 4.3.1) | robotpkg-ros2-rosidl (= 4.9.0r1) | robotpkg-ros2-rosidl (= 5.3.1) | robotpkg-ros2-rosidl (= 4.9.0), robotpkg-ros2-ros-workspace (= 1.0.2) | robotpkg-ros2-ros-workspace (= 1.0.3), robotpkg-ros2-rmw-dds-common (= 6.1.0) | robotpkg-ros2-rmw-dds-common (= 2.1.0) | robotpkg-ros2-rmw-dds-common (= 3.1.0), robotpkg-ros2-rcutils (= 6.3.0) | robotpkg-ros2-rcutils (= 7.2.0) | robotpkg-ros2-rcutils (= 6.10.1), robotpkg-ros2-rcpputils (= 2.13.4) | robotpkg-ros2-rcpputils (= 2.4.0) | robotpkg-ros2-rcpputils (= 2.12.0) | robotpkg-ros2-rcpputils (= 2.15.0), robotpkg-py310-ament-package (= 0.18.0) | robotpkg-py310-ament-package (= 0.14.0), robotpkg-fastdds+doc (= 3.6.1) | robotpkg-fastdds (= 3.6.1), robotpkg-fastcdr (= 2.3.0) | robotpkg-fastcdr+doc (= 1.1.1) | robotpkg-fastcdr+doc (= 2.3.0) | robotpkg-fastcdr (= 1.1.1) | robotpkg-fastcdr (= 2.3.6) | robotpkg-fastcdr+doc (= 2.3.6), libstdc++6, python3-empy (>= 3), libtinyxml2-dev (>= 2)
Conflicts: robotpkg-ros2-rmw-fastrtps
Provides: robotpkg-ros2-rmw-fastrtps
Replaces: robotpkg-ros2-rmw-fastrtps
Description: ROS2 Middleware interface using Fast RTPS
 License: apache-2.0
 Debian-Packager: robotpkg@laas.fr
 rmw_fastrtps actually provides not one but two different ROS 2 middleware
 implementations, both of them using Fast DDS as middleware layer:
 rmw_fastrtps_cpp and rmw_fastrtps_dynamic_cpp (note that directory
 rmw_fastrtps_shared_cpp just contains the code that the two implementations
 share, and does not constitute a layer on its own).
 .
 The main difference between the two is that rmw_fastrtps_dynamic_cpp uses
 introspection typesupport at run time to decide on the
 serialization/deserialization mechanism. On the other hand, rmw_fastrtps_cpp
 uses its own typesupport, which generates the mapping for each message type at
 build time.
 .
 Mind that the default ROS 2 RMW implementation is rmw_fastrtps_cpp. You can
 however set it to rmw_fastrtps_dynamic_cpp using the environment variable
 RMW_IMPLEMENTATION.
 .
 Homepage:
 https://github.com/rmw_fastrtps/

