Install Linux Host Dependencies¶
Go back to the main Getting Started Guide when you’re done here.
Documentation is available for these Linux distributions:
- Ubuntu 16.04 LTS or 18.04 LTS 64-bit
- Fedora 28 64-bit
- Clear Linux
- Arch Linux
Update Your Operating System¶
Ensure your host system is up to date.
sudo apt-get update sudo apt-get upgrade
sudo dnf upgrade
sudo swupd update
sudo pacman -Syu
Install Requirements and Dependencies¶
Note that both Ninja and Make are installed with these instructions; you only need one.
sudo apt-get install --no-install-recommends git cmake ninja-build gperf \ ccache dfu-util device-tree-compiler wget \ python3-pip python3-setuptools python3-tk python3-wheel xz-utils file \ make gcc gcc-multilib
sudo dnf group install "Development Tools" "C Development Tools and Libraries" dnf install git cmake ninja-build gperf ccache dfu-util dtc wget \ python3-pip python3-tkinter xz file glibc-devel.i686 libstdc++-devel.i686
sudo swupd bundle-add c-basic dev-utils dfu-util dtc \ os-core-dev python-basic python3-basic python3-tcl
The Clear Linux focus is on native performance and security and not cross-compilation. For that reason it uniquely exports by default to the environment of all users a list of compiler and linker flags. Zephyr’s CMake build system will either warn or fail because of these. To clear the C/C++ flags among these and fix the Zephyr build, run the following command as root then log out and back in:
# echo 'unset CFLAGS CXXFLAGS' >> /etc/profile.d/unset_cflags.sh
Note this command unsets the C/C++ flags for all users on the
system. Each Linux distribution has a unique, relatively complex and
potentially evolving sequence of bash initialization files sourcing each
other and Clear Linux is no exception. If you need a more flexible
solution, start by looking at the logic in
sudo pacman -S git cmake ninja gperf ccache dfu-util dtc wget \ python-pip python-setuptools python-wheel tk xz file make
CMake version 3.13.1 or higher is required. Check what version you have by
cmake --version. If you have an older version, there are several ways
of obtaining a more recent one:
pip3 install --user cmake
Download and install from the pre-built binaries provided by the CMake project itself in the CMake Downloads page. For example, to install version 3.13.1 in
mkdir $HOME/bin/cmake && cd $HOME/bin/cmake wget https://github.com/Kitware/CMake/releases/download/v3.13.1/cmake-3.13.1-Linux-x86_64.sh yes | sh cmake-3.13.1-Linux-x86_64.sh | cat echo "export PATH=$PWD/cmake-3.13.1-Linux-x86_64/bin:\$PATH" >> $HOME/.zephyrrc
Check your distribution’s beta or unstable release package library for an update.
You might also want to uninstall the CMake provided by your package manager to avoid conflicts.
Install the Zephyr Software Development Kit (SDK)¶
Use of the Zephyr SDK is optional, but recommended. Some of the dependencies installed above are only needed for installing the SDK.
Zephyr’s SDK contains all necessary tools to build Zephyr on all supported architectures. Additionally, it includes host tools such as custom QEMU binaries and a host compiler. The SDK supports the following target architectures:
- X86 IAMCU ABI
- Nios II
Follow these steps to install the Zephyr SDK:
Download the latest SDK as a self-extracting installation binary:
(You can change 0.10.1 to another version if needed; the Zephyr Downloads page contains all available SDK releases.)
Run the installation binary, installing the SDK at
cd <sdk download directory> ./zephyr-sdk-0.10.1-setup.run -- -d ~/zephyr-sdk-0.10.1
You can pick another directory if you want. If this fails, make sure Zephyr’s dependencies were installed as described in Install Requirements and Dependencies.
Set these environment variables:
$HOME/zephyr-sdk-0.10.1(or wherever you chose to install the SDK)
If you ever want to uninstall the SDK, just remove the directory where you installed it and unset these environment variables.
Building on Linux without the Zephyr SDK¶
The Zephyr SDK is provided for convenience and ease of use. It provides toolchains for all Zephyr target architectures, and does not require any extra flags when building applications or running tests. In addition to cross-compilers, the Zephyr SDK also provides prebuilt host tools. It is, however, possible to build without the SDK’s toolchain by using another toolchain as as described in the main Getting Started Guide document.
As already noted above, the SDK also includes prebuilt host tools. To use the
SDK’s prebuilt host tools with a toolchain from another source, keep the
ZEPHYR_SDK_INSTALL_DIR environment variable set to the Zephyr SDK
installation directory. To build without the Zephyr SDK’s prebuilt host tools,
ZEPHYR_SDK_INSTALL_DIR environment variable must be unset before
source zephyr-env.sh later on in the Getting Started Guide.
To make sure this variable is unset, run: