|Raspbian Stretch||ARMv6||All RaspberryPis: Classic, Zero, 2, 3||5.1.5|
|Raspbian Buster||ARMv6||All RaspberryPis: Classic, Zero, 2, 3, 4||5.1.5|
|Debian Stretch||ARMv7||Every ARMv7 board, RaspberryPis 2/3 included||5.1.5|
|Debian Buster||ARMv7||Every ARMv7 board, RaspberryPis 2/3/4 included||5.1.5|
|Ubuntu 16.04||ARMv7||All versions of RaspberryPi 2/3, other ARMv7 boards||5.1.5|
|Ubuntu 18.04||ARMv7||All versions of RaspberryPi 2/3/4, other ARMv7 boards||5.1.5|
|Ubuntu 16.04/18.04||aarch64||All versions of RaspberryPi 3/4, other ARMv7 boards||5.1.3: swift-arm64|
|Fedora/CentOS/RHEL||aarch64||All versions of RaspberryPi 3/4, other ARMv7 boards||5.1.4:
For binaries of older releases, check out the releases page.
For alternative ways to install these Swift binaries on your ARM board, check out Swift on Balena by Will Lisac, Helge Heß's dockSwiftOnARM, both based on Docker, and the Swift Deb Repository maintained by Neil Jones.
To quickly cross-compile your Swift applications for ARM on a Mac (a time saver) check out the Swift Cross Compilation Toolchains project built by Van Simmons.
When using the Swift Package Manager on one of these boards, that usually have limited memory/cpu, you'll need to use the new
-j option to reduce the number of threads spawned by the tool and be able to compile.
For example, when building an SPM project most of the times we'll limit the number of jobs to one:
[email protected]:> swift build -j 1
In order to use the provided prebuilt binaries you'll need to install the following dependencies:
Raspbian Stretch and Ubuntu 16.04
sudo apt install clang-3.8 libicu-dev libcurl4-nss-dev sudo update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-3.8 100 sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-3.8 100
Raspbian Buster, Ubuntu 18.04 and newer
sudo apt install clang libicu-dev libcurl4-nss-dev curl
Decompress the archive on the RaspberryPi, you'll find the Swift binaries in
usr/bin/ relative to where you decompressed the archive.
tar -xzf <archivename.tgz>
Ensure that the path you decompressed to is in your
PATH environment variable:
echo $PATH. If it's not then add it to your path for your shell.
To permanently add this to your
PATH variable, you can add the following block of code to the end of your
if [ -d "$HOME/usr/bin" ] ; then PATH="$HOME/usr/bin:$PATH" fi
Verify the swift version is setup:
$ swift --version Swift version 5.1.3 (swift-5.1.3-RELEASE) Target: armv7-unknown-linux-gnueabihf
For the latest updates on Swift on ARM, check out my blog here.
Check out Helge Heß's project dockSwiftOnARM to build Swift in a Docker container or to build a cross-compiling toolchain that will allow you to build arm binaries directly from your Mac using a precompiled swiftc for ARM.
The scripts that buildSwiftOnARM provides:
clone.sh - Install dependencies and clones the main Swift repository and all the related projects
checkoutRelease.sh - Resets all repos, updates them, checks out a specific tag (5.1.3 at the moment) and apply the patches.
build.sh - Builds Swift producing a tgz archive with the Swift distributions.
clean.sh - Cleans all build artifacts, only needed when you want to start again from scratch.
First of all, use a suitably sized sd-card, at least 32Gb in size, but I recommend to use an external USB drive to clone the project and build Swift.
Configure a swap file of at least 2Gb, on Ubuntu:
sudo fallocate -l 2G swapfile sudo chmod 600 swapfile sudo mkswap swapfile sudo swapon swapfile
You'll need to manually enable the swap file with
swapon each time you reboot the RaspberryPi (or the system will just run without swap).
On Raspbian, since the swapfile is already configured, open
/etc/dphys-swapfile and edit
CONF_SWAPSIZE to increase the size:
Save the file and:
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start
Now, call the included scripts as follows:
clone.sh that will install the required dependencies (git cmake ninja-build clang-3.8 python uuid-dev libicu-dev icu-devtools libbsd-dev libedit-dev libxml2-dev libsqlite3-dev swig libpython-dev libncurses5-dev pkg-config libblocksruntime-dev libcurl4-openssl-dev autoconf libtool systemtap-sdt-dev libcurl4-openssl-dev libz-dev), fix clang links and clone apple/swift with all its dependecies.
checkoutRelease.sh that will select the current release (5.1.3) and apply the needed patches.
Once done, start the build with
Once the build completes a few hours later, you'll have a
swift-5.1.3-armv7.tgz archive containing the whole Swift compiler distribution. Once decompressed you'll find the Swift binaries under
I recommend to perform all these operations in a permanent background
screen session (
CTRL+B d to detach from the session and
tmux a to reattach to it when you ssh again into the RaspberryPi).
Additional steps could be required in some cases check the latest ARM posts on my blog for additional info.
To build a different release than the one currently configured in the script, open
build.sh and modify the variables on top, with the branch name for the release and the release name for the tgz respectively.
If you need to replicate a setup like the one I use to build all the Swift binaries you can find above, using only a single Raspberry Pi 4 or a similar board ARMv7 board as build machine, check out buildSwiftOnARMInfra with its docker containers.
ARM projects can be tested in an environment simulated through QEMU on GitHub using the Run-On-Architecture action. While you will not be able to use hardware interfaces available on real ARM boards, this environment should be more than enough to perform some basic testing or even build your projects and deploy them directly to your target ARM board (with considerable time savings).
Since the first releases of Swift on ARM32, the REPL has never been available on this platform, but that doesn't impact the compiler itself. Considering this, as you would expect, launching
swift without parameters will result in an error instead of the REPL prompt.
We wouldn't have Swift on ARM and most of the patches included on buildSwiftOnARM without the work done by these developers:
The community can be reached at the swift-arm Slack channel.
You can compile old releases checking out the specific tag: