Skip to content

Releases: eProsima/ROS2-SH

v.3.1.0

23 Jun 07:16
@lauramg15 lauramg15
v3.1.0
0ec37df
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v.3.1.0 Latest
Latest
  • Cross-compatibility with ROS 2 Galactic.
  • Added IS_ROS2_DISTRO compilation flag to select which ROS 2 version will be used.
  • Avoid communication between internal publishers and subscribers on the same topic, solving the infinite loop problem.
  • Unify CMakeLists to avoid creation of empty folders when the tests are not compiled.
  • New issue badge to open issues only in the main repository.
Assets 2
Loading

v3.0.0

21 May 10:33
@jamoralp jamoralp
v3.0.0
da1a443
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.0

  • Completed migration from SOSS to Integration Service. This, code wise, included changing the C++ namespace convention of the whole project, from soss::ros2 to eprosima::is::sh::ros2.

  • Used eProsima xTypes as the common language for the ROS 2 System Handle to speak to the Core.

  • Debug logging traces are automatically enabled if the project is compiled in debug mode.

  • Add much more traces and unify the logging style.

  • Full API reference documentation using Doxygen.

  • Migrated whole test suite from Catch to Google Test.

  • Applied uncrustify rules.

  • Added brand new README section, with detailed information about the project status and features.

  • Created a ROS2-SH GitHub action automated task.

  • Added global and specific compilation flags.

  • Rearranged project folders with a more consistent structure.

  • Created a new MIX generator project to ease users the task of compiling custom
    ROS 2 packages transformation libraries.

  • Fixed service server/client not taking into account request and reply types separately.

Loading