[^1]: Binaries for these pairings are provided from a the packages.osrfoundation.org repository. Refer to https://gazebosim.org/docs/latest/ros_installation for installation instructions.

For information on ROS 2 and Gazebo compatibility, refer to the melodic branch README

Please ticket an issue if you'd like support to be added for some combination.

Details about the renaming process from ign to gz .

Note: The ros_ign prefixed packages are shim packages that redirect to their ros_gz counterpart. Under most circumstances you want to be using the ros_gz counterpart.

Integration between ROS and Gazebo

Packages

This repository holds packages that provide integration between ROS and Gazebo:

• ros_gz: Metapackage which provides all the other packages.
• ros_gz_image: Unidirectional transport bridge for images from Gazebo Transport to ROS using image_transport.
• ros_gz_bridge: Bidirectional transport bridge between Gazebo Transport and ROS.
• ros_gz_sim: Convenient launch files and executables for using Gazebo Sim with ROS.
• ros_gz_sim_demos: Demos using the ROS-Gazebo integration.
• ros_gz_point_cloud: Plugins for publishing point clouds to ROS from Gazebo Sim simulations.

Install

This branch supports ROS Humble. See above for other ROS versions.

Binaries

Humble binaries are available for Fortress. They are hosted at https://packages.ros.org.

1. Add https://packages.ros.org

   sudo sh -c 'echo "deb [arch=$(dpkg --print-architecture)] http://packages.ros.org/ros2/ubuntu $(lsb_release -cs) main" > /etc/apt/sources.list.d/ros2-latest.list'
   curl -s https://raw.githubusercontent.com/ros/rosdistro/master/ros.asc | sudo apt-key add -
   sudo apt-get update
   

2. Install ros_gz

   sudo apt install ros-humble-ros-gz
   

From source

ROS

Be sure you've installed ROS Humble (at least ROS-Base). More ROS dependencies will be installed below.

Gazebo

Install either Edifice, Fortress, or Garden.

Set the GZ_VERSION environment variable to the Gazebo version you'd like to compile against. For example:

export GZ_VERSION=edifice # IMPORTANT: Replace with correct version

You only need to set this variable when compiling, not when running.

Compile ros_gz

The following steps are for Linux and OSX.

1. Create a colcon workspace:

    # Setup the workspace
    mkdir -p ~/ws/src
    cd ~/ws/src

    # Download needed software
    git clone https://github.com/gazebosim/ros_gz.git -b humble

1. Install dependencies (this may also install Gazebo):

    cd ~/ws
    rosdep install -r --from-paths src -i -y --rosdistro humble

> If `rosdep` fails to install Gazebo libraries and you have not installed them before, please follow [Gazebo installation instructions](https://gazebosim.org/docs/latest/install).

1. Build the workspace:

    # Source ROS distro's setup.bash
    source /opt/ros/<distro>/setup.bash

    # Build and install into workspace
    cd ~/ws
    colcon build

[!TIP] The ros_gz library makes heavy use of templates which causes compilers to consume a lot of memory. If your build fails with c++: fatal error: Killed signal terminated program cc1plus try building with colcon build --parallel-workers=1 --executor sequential. You might also have to set export MAKEFLAGS="-j 1" before running colcon build to limit the number of processors used to build a single package.

If `colcon build` fails with [this issue](https://github.com/gazebosim/ros_gz/issues/401)

    CMake Error at CMakeLists.txt:81 (find_package):
      By not providing "Findactuator_msgs.cmake" in CMAKE_MODULE_PATH this
      project has asked CMake to find a package configuration file provided by
      "actuator_msgs", but CMake did not find one.

    cd src
    git clone git@github.com:rudislabs/actuator_msgs.git
    cd ../
    colcon build

ROSCon 2022

Project Template

A template project integrating ROS and Gazebo simulator

Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:

5. Submission of Contributions. Unless You explicitly state otherwise,
   any Contribution intentionally submitted for inclusion in the Work
   by You to the Licensor shall be under the terms and conditions of
   this License, without any additional terms or conditions.
   Notwithstanding the above, nothing herein shall supersede or modify
   the terms of any separate license agreement you may have executed
   with Licensor regarding such Contributions.