Installing ROS 2 on macOS¶
Table of Contents
This page explains how to install ROS 2 on macOS from a pre-built binary package.
The pre-built binary does not include all ROS 2 packages. All packages in the ROS base variant are included, and only a subset of packages in the ROS desktop variant are included. The exact list of packages are described by the repositories listed in this ros2.repos file.
We currently support macOS Mojave (10.14). The Rolling Ridley distribution will change target platforms from time to time as new platforms become available. Most people will want to use a stable ROS distribution.
You need the following things installed before installing ROS 2.
brew (needed to install more stuff; you probably already have this):
Follow installation instructions at http://brew.sh/
Optional: Check that
brewis happy with your system configuration by running:
brew doctor Fix any problems that it identifies.
brewto install more stuff:
brew install firstname.lastname@example.org # Unlink in case you have email@example.com installed already brew unlink python # Make the python command be Python 3.8 brew link --force firstname.lastname@example.org # install asio and tinyxml2 for Fast-RTPS brew install asio tinyxml2 # install dependencies for robot state publisher brew install tinyxml eigen pcre poco # OpenCV isn't a dependency of ROS 2, but it is used by some demos. brew install opencv # install OpenSSL for DDS-Security brew install openssl # if you are using ZSH, then replace '.bashrc' with '.zshrc' echo "export OPENSSL_ROOT_DIR=$(brew --prefix openssl)" >> ~/.bashrc # install Qt for RViz brew install qt freetype assimp # install console_bridge for rosbag2 brew install console_bridge # install dependencies for rcl_logging_log4cxx brew install log4cxx spdlog # install CUnit for Cyclone DDS brew install cunit
Install rqt dependencies
brew install sip pyqt5
Fix some path names when looking for sip stuff during install (see ROS 1 wiki):
ln -s /usr/local/share/sip/Qt5 /usr/local/share/sip/PyQt5
brew install graphviz
python3 -m pip install pygraphviz pydot
You may run into an issue installing
pygraphviz, “error: Error locating graphviz”. Try the following install command instead:
python3 -m pip install --install-option="--include-path=/usr/local/include/" --install-option="--library-path=/usr/local/lib/" pygraphviz
Install SROS2 dependencies
python3 -m pip install lxml
Install additional runtime dependencies for command-line tools:
python3 -m pip install argcomplete catkin_pkg empy ifcfg importlib-metadata lark-parser lxml netifaces numpy pyparsing pyyaml setuptools
macOS/OS X versions >=10.11 have System Integrity Protection enabled by default.
So that SIP doesn’t prevent processes from inheriting dynamic linker environment variables, such as
DYLD_LIBRARY_PATH, you’ll need to disable it following these instructions.
Binary releases of Rolling Ridley are not provided. Instead you may download nightly prerelease binaries.
Download the latest package for macOS; let’s assume that it ends up at
Note: there may be more than one binary download option which might cause the file name to differ.
mkdir -p ~/ros2_rolling cd ~/ros2_rolling tar xf ~/Downloads/ros2-package-osx-x86_64.tar.bz2
If you would like to use another DDS or RTPS vendor besides the default, eProsima’s Fast RTPS, you can find instructions here.
In one terminal, set up the ROS 2 environment as described above and then run a C++
ros2 run demo_nodes_cpp talker
In another terminal, set up the ROS 2 environment and then run a Python
ros2 run demo_nodes_py listener
You should see the
talker saying that it’s
Publishing messages and the
I heard those messages.
This verifies both the C++ and Python APIs are working properly.
Continue with the tutorials and demos 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
Fast-RTPS, but the middleware (RMW) can be replaced at runtime.
See the tutorial on how to work with multiple RMWs.
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
setupfile. 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