From ArchWiki
Jump to navigation Jump to search

ROS is an open-source, meta-operating system for your robot. It provides the services you would expect from an operating system, including hardware abstraction, low-level device control, implementation of commonly-used functionality, message-passing between processes, and package management.

Installation Instructions

You can install any of the ROS distributions below since they are fully released on AUR.

Melodic ros-melodic-desktop-fullAUR

Lunar ros-lunar-desktop-fullAUR

Older Versions (Not fully working)


Kinetic packages on the AUR are a work in progress. There are some issues regarding opencv3 that have not been fully resolved yet (installing ros-kinetic-opencv3AUR works, but is somewhat inefficient since it rebuilds opencv3). Currently, installing a metapackage such as ros-kinetic-ros-coreAUR or ros-kinetic-robotAUR should bring in all required dependencies (see [1] for the correct order).

Packages are being added on an as-needed basis. Please post any issues with the current packages in their respective AUR comments section.


Note that catkin uses python2, and therefore catkin_make may fail unless it explicitly uses python2. To do so, add the following alias to ~/.bashrc:

alias catkin_make="catkin_make -DPYTHON_EXECUTABLE=/usr/bin/python2 -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/"

Another way is to use python-catkin_toolsAUR and to configure it by running the following command in your Catkin workspace.

catkin config --cmake-args -DPYTHON_EXECUTABLE=/usr/bin/python2

Using Catkin/ROS with an IDE


To make CLionAUR support ROS packages, you can change the Exec parameter of its desktop file ( ~/.local/share/applications/jetbrains-clion.desktop) as follows.

Exec=bash -i -c "source /home/[username]/catkin_ws/devel/;/opt/clion/bin/" %f

However, /home/[username]/catkin_ws must be exchanged with your Catkin workspace. You can now open a Catkin project without cmake complaining about missing packages, hopefully. If desired or needed you can use Python 3 by adding -DPYTHON_EXECUTABLE=/usr/bin/python3 to the CMake options which can be found in the settings.

catkin build

For configuring the systems using the catkin build environment, one have to configure the catkin workspace as usual and issue a

catkin config -DPYTHON_EXECUTABLE=/usr/bin/python2 -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/

Afterwards, use catkin build as normal. Please remember to reconfigure your catkin whenever you delete the configuration files (i.e. the catkin_ws directory)

Rebuild when shared libraries are updated

When you update a library that ROS depends on (e.g. Boost), all packages that link to it must be rebuilt. Most AUR helpers will not detect this situation. The following script will generate a list of all packages that are linked to missing so files:

(Note that the script requires pyalpm to be installed.)


Building from source

Build instructions are available at

Install build dependencies: wget, python, python-yaml, python-setuptools, sip, python-sip, python-pyqt5, git, cmake, asio, tinyxml, tinyxml2, eigen, libxaw, glu, qt5-base, opencv, hdf5, vtk, glew, poco, python-nose, python-numpy, python-lark-parser, python-vcstoolAUR, python-empyAUR, log4cxxAUR, python-colcon-common-extensionsAUR, python-rosdepAUR.

Fetch the sources:

$ mkdir -p ~/ros2_ws/src
$ cd ~/ros2_ws
$ wget
$ vcs import src < ros2.repos

Presently some fixes are required:

Edit build/qt_gui_cpp/sip/qt_gui_cpp_sip/Makefile:12, replacing $$[QT_INSTALL_LIBS] with /usr/lib. Github issue

Now you can build the workspace:

$ cd ~/ros2_ws
$ colcon build --symlink-install

Read regarding ROS 1 / ROS 2 interoperability.

Usage Examples

First source the workspace:

$ . ~/ros2_ws/install/local_setup.bash

Functionality comparable to roscore, rosnode, rostopic, rosmsg, rospack, rosrun and rosservice is available via ros2:

$ ros2 -h
usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ... 

ros2 is an extensible command-line tool for ROS 2.

optional arguments:
  -h, --help            show this help message and exit

  daemon    Various daemon related sub-commands
  msg       Various msg related sub-commands
  node      Various node related sub-commands
  pkg       Various package related sub-commands
  run       Run a package specific executable
  security  Various security related sub-commands
  service   Various service related sub-commands
  srv       Various srv related sub-commands
  topic     Various topic related sub-commands

  Call `ros2 <command> -h` for more detailed usage.

A typical "Hello World" example starts with running a publisher node:

$ ros2 topic pub /chatter 'std_msgs/String' "data: 'Hello World'"

Then, in another terminal, you can run a subscriber (Don't forget to source the workspace in every new terminal):

$ ros2 topic echo /chatter

List existing nodes:

$ ros2 node list

List topics:

$ ros2 topic list

ROS 2's version of rviz is

$ rviz2