QPi is an attempt to create a convenient Qt SDK for the Raspberry Pi 0/1/2/3 on Arch Linux. You click a button in Qt Creator, your application is automagically deployed and run on the board, without X11 involvement. (The tooling facilitates this, this is primarily a packaging initiative with a little polish required)


The primary goal is to ensure full functionality of Qt on the Raspberry Pi, and to ease the overhead/complexity of cross compilation from desktop Arch installs to Arch based Raspberry Pis.

Qt can run quite nicely on the Pi(s), as long as you are not running it under Xorg/X11. The packaged versions of Qt run the gamut, but I have yet to see a Qt packaging which targets kms/console usage, or which has functional wayland support (outside of Intel hardware) as shipped.

I happen to be a big fan of cross compilation rather than compilation on target, which simply removes all joy from iterative development. We provide 2 packages, one for the Raspberry Pi and one for the host machine, which once installed allow you to cross compile for the Raspberry Pi from your Arch host machine. These packages are simply tar balls, so they should even run outside of Arch in a suitably modern Linux install. (The packaging is frosting)

Project Status

  • Qt 5.9.0 is fully functional on the Raspberry Pi 1/2
  • CEC input support is currently alpha

Known issues

  • One step is required to get remote deployment working: navigate to Tools/Options/Devices/Devices. Select Raspberry Pi # from the drop down, adjust the password as necessary and then hit the test button. Deployment will not work until you hit test, even if all the parameters are correct.
  • You need the rootfs to be available at the appropriate location. Welcome to cross compiling. Either copy it to your compile host, or compile against an nfs mount of your Raspberry Pi. Mounting the rootfs (“/”) of your Raspberry Pi 2 to /mnt/pi2 (via NFS) does the task nicely.
  • Single applications can run well with eglfs at 1080p. I have not been able to get wayland working well on the Raspberry Pi at anything other than 720p.
  • aarch64 support is barred by numerous logistic issues at present.
  • Allocate lots of graphical memory if you intend to run GLES2 apps. I allocate 512 MB on the Raspberry Pi 2 and 256 MB on the Pi Zero.

Packaging choices

  • Excluded Qt WebEngine (not a point of personal interest)
  • Excluded Qt Script (legacy)

build from AUR if you want/need this functionality.

Platform Notes

Raspberry Pi 0/1(armv6)2/3(armv7)

uses the vc stack and the propietary drivers/blobs (and has CEC support). 2 Packages split along architectual lines.

Raspberry Pi 3 (aarch64)

uses the mesa stack.

AUR recipes

These AUR recipe(s) are used to generate my Qt SDK packages

Arch repo

SigLevel = Optional
Server =$arch

This repo is equipped with packages generated by the above recipe, packages you can either directly consume, or ingest by way of magical (read dangerous) bash scripts which you can embrace in disdain for your sovereignty. Proceed at your own risk, and neither myself nor my employer provide any binding guarantees or assurances. Kiss your poodle goodbye.


  1. Proceed at your own risk
  2. Install the appropriate Arch on a fresh sd card
  3. Boot the Raspberry Pi
  4. Download and run the following script on the RPI
  5. I personally normally do this by allowing root login via ssh and then grabbing the script via curl
  6. curl >
  7. bash
  8. I would strongly recommend increasing the video ram to 512 in /boot/config.txt. When using the mesa stack (The Pi 3) the contents of config.txt are ignored, and you have to stipulate the graphical memory via a kernel commandline argument: cma=512
  9. Run this script on your Arch host machine
  10. Mount your Arch sysroot on your host (recommend NFS, mounting “/” under /mnt/pi{version})
  11. You are now set to use Qt Creator to develop and deploy to your Raspberry Pi
  12. Please note, you might have to explicitly “test” the device in the device page of Qt Creator in order for deployment to work. (pessimistic)