.. redirect-from:: Installation/Linux-Development-Setup
Table of Contents
- System requirements
- System setup
- Get ROS 2 code
- Install dependencies using rosdep
- Install additional DDS implementations (optional)
- Build the code in the workspace
- Environment setup
- Try some examples
- Next steps after installing
- Using the ROS 1 bridge
- Additional RMW implementations (optional)
- Alternate compilers
- Stay up to date
- Troubleshooting
- Uninstall
The current Debian-based target platforms for Rolling Ridley are:
- Tier 1: Ubuntu Linux - Focal Fossa (20.04) 64-bit
- Tier 3: Debian Linux - Bullseye (11) 64-bit
Other Linux platforms with varying support levels include:
- Arch Linux, see alternate instructions
- Fedora Linux, see alternate instructions <Fedora-Development-Setup>
- OpenEmbedded / webOS OSE, see alternate instructions
As defined in REP 2000.
sudo apt update && sudo apt install -y \
build-essential \
cmake \
git \
python3-colcon-common-extensions \
python3-flake8 \
python3-pip \
python3-pytest-cov \
python3-rosdep \
python3-setuptools \
python3-vcstool \
wget
# install some pip packages needed for testing
python3 -m pip install -U \
flake8-blind-except \
flake8-builtins \
flake8-class-newline \
flake8-comprehensions \
flake8-deprecated \
flake8-docstrings \
flake8-import-order \
flake8-quotes \
pytest-repeat \
pytest-rerunfailures \
pytest \
setuptools
Ubuntu 18.04 is not an officially supported platform, but may still work. You'll need at least the following additional dependencies:
python3 -m pip install -U importlib-metadata importlib-resources
Create a workspace and clone all repos:
mkdir -p ~/ros2_rolling/src
cd ~/ros2_rolling
wget https://raw.githubusercontent.com/ros2/ros2/master/ros2.repos
vcs import src < ros2.repos
sudo rosdep init
rosdep update
rosdep install --from-paths src --ignore-src --rosdistro rolling -y --skip-keys "console_bridge fastcdr fastrtps rti-connext-dds-5.3.1 urdfdom_headers"
If you would like to use another DDS or RTPS vendor besides the default, eProsima's Fast RTPS, you can find instructions here <DDS-Implementations>.
If you have already installed ROS 2 another way (either via Debians or the binary distribution), make sure that you run the below commands in a fresh environment that does not have those other installations sourced.
Also ensure that you do not have source /opt/ros/${ROS_DISTRO}/setup.bash
in your .bashrc
.
You can make sure that ROS 2 is not sourced with the command printenv | grep -i ROS
.
The output should be empty.
More info on working with a ROS workspace can be found in this tutorial </Tutorials/Colcon-Tutorial>.
cd ~/ros2_rolling/
colcon build --symlink-install
Note: if you are having trouble compiling all examples and this is preventing you from completing a successful build, you can use COLCON_IGNORE
in the same manner as CATKIN_IGNORE to ignore the subtree or remove the folder from the workspace.
Take for instance: you would like to avoid installing the large OpenCV library.
Well then simply $ touch COLCON_IGNORE
in the cam2image
demo directory to leave it out of the build process.
Set up your environment by sourcing the following file.
. ~/ros2_rolling/install/local_setup.bash
In one terminal, source the setup file and then run a C++ talker
:
. ~/ros2_rolling/install/local_setup.bash
ros2 run demo_nodes_cpp talker
In another terminal source the setup file and then run a Python listener
:
. ~/ros2_rolling/install/local_setup.bash
ros2 run demo_nodes_py listener
You should see the talker
saying that it's Publishing
messages and the listener
saying I heard
those messages.
This verifies both the C++ and Python APIs are working properly.
Hooray!
Continue with the tutorials and demos </Tutorials> to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
The ROS 1 bridge can connect topics from ROS 1 to ROS 2 and vice-versa. See the dedicated documentation on how to build and use the ROS 1 bridge.
The default middleware that ROS 2 uses is Cyclone DDS
, but the middleware (RMW) can be replaced at runtime.
See the guide <../Guides/Working-with-multiple-RMW-implementations> on how to work with multiple RMWs.
Using a different compiler besides gcc to compile ROS 2 is easy. If you set the environment variables CC
and CXX
to executables for a working C and C++ compiler, respectively, and retrigger CMake configuration (by using --force-cmake-config
or by deleting the packages you want to be affected), CMake will reconfigure and use the different compiler.
To configure CMake to detect and use Clang:
sudo apt install clang
export CC=clang
export CXX=clang++
colcon build --cmake-force-configure
See :ref:`MaintainingSource` to periodically refresh your source installation.
Troubleshooting techniques can be found :ref:`here <linux-troubleshooting>`.
If you installed your workspace with colcon as instructed above, "uninstalling" could be just a matter of opening a new terminal and not sourcing the workspace's
setup
file. This way, your environment will behave as though there is no Rolling install on your system.If you're also trying to free up space, you can delete the entire workspace directory with:
rm -rf ~/ros2_rolling