Appendix A: Building the Client

This section explains how to build the ownCloud Client from source for all major platforms. You should read this section if you want to develop for the desktop client. Build instructions are subject to change as development proceeds.

Please check the version for which you want to build.

These instructions are updated to work with version of the ownCloud Client.

Compiling via ownBrander

If you don’t want to go through the trouble of doing all the compile work manually, you can use ownBrander to create installer images for all platforms.

Getting the Source Code

The generic build instructions pull the latest code directly from GitHub, and work on Linux, Mac OS X, and Windows.


For the published desktop clients we link against QT5 dependencies from our own repositories so that we can have the same versions on all distributions. This chapter shows you how to build the client yourself with this setup. If you want to use the QT5 dependencies from your system, see the next chapter.

You may wish to use source packages for your Linux distribution, as these give you the exact sources from which the binary packages are built. These are hosted on the ownCloud repository from OBS. Go to the Index of repositories to see all the Linux client repositories.

To get the .deb source packages, add the source repository for your Debian or Ubuntu version, as in the following example for Debian 9:

# Run as root
echo 'deb-src /' >> /etc/apt/sources.list.d/owncloud-client.list

Install the dependencies using the following commands for your specific Linux distribution. Make sure the repositories for source packages are enabled. These are:

Distribution Installation Instructions


apt update; apt build-dep owncloud-client


zypper ref; zypper si -d owncloud-client


yum install yum-utils; yum-builddep owncloud-client

Follow the generic build instructions, starting with step 2.

Linux with System Dependencies

Build sources from a GitHub checkout with dependencies provided by your Linux distribution. While this allows more freedom for development, it does not exactly represent what we ship as packages. See above for how to recreate packages from source.

To get the source dependencies on Debian and Ubuntu, run the following command:

sudo apt install qtdeclarative5-dev libinotifytools-dev \
  qt5keychain-dev libqt5webkit5-dev python-sphinx \

Follow the generic build instructions, starting with step 1.


In addition to needing Xcode (along with the command line tools), developing in the macOS environment requires extra dependencies. You can install these dependencies through MacPorts or Homebrew. These dependencies are required only on the build machine, because non-standard libs are deployed in the app bundle.

The tested and preferred way to develop in this environment is through the use of HomeBrew. The ownCloud team has its own repository containing non-standard recipes. To set up your build environment for development using HomeBrew:

  1. Install Xcode.

  2. Install Xcode command line tools using xcode-select –install.

  3. Install Homebrew using /usr/bin/ruby -e $(curl -fsSL

  4. Add the ownCloud repository using the command brew tap owncloud/owncloud

  5. Install a Qt5 version, ideally from from 5.10.1, using the command brew install qt5.

  6. Install any missing dependencies, using the command: brew install $(brew deps owncloud-client).

  7. Install qtkeychain by running git clone Make sure you make the same install prefix as later while building the client e.g., -DCMAKE_INSTALL_PREFIX=/Path/to/client/../install.

  8. For compilation of the client, follow the generic build instructions.

  9. Install the Packages package creation tool.

  10. In the build directory, run admin/osx/ <CMAKE_INSTALL_DIR> <build dir> <installer sign identity>. If you have a developer signing certificate, you can specify its Common Name as a third parameter (use quotes) to have the package signed automatically.

Contrary to earlier versions, version 1.7 and later are packaged as a pkg installer. Do not call make package at any time when compiling for OS X, as this will build a disk image, which will not work correctly.

Windows Development Build

If you want to test some changes and deploy them locally, you can build natively on Windows using MinGW. If you want to generate an installer for deployment, please follow Windows Installer Build (Cross-Compile) instead.

  1. Get the required dependencies

    • Make sure that you have CMake and Git.

    • Download the Qt MinGW package. You will use the MinGW version bundled with it.

    • Download an OpenSSL Windows Build (the non-'Light' version)

  2. Get the QtKeychain sources as well as the latest versions of the ownCloud client from Git as follows:

    git clone
    git clone git://
  1. Open the Qt MinGW shortcut console from the Start Menu

  2. Make sure that OpenSSL’s bin directory as well as your QtKeychain source directories are in your PATH. This will allow CMake to find the library and headers, as well as allow the ownCloud client to find the DLLs at runtime:

    set PATH=C:\<OpenSSL Install Dir>\bin;%PATH%
    set PATH=C:\<qtkeychain Clone Dir>;%PATH%
  1. Build qtkeychain directly in the source directory so that the DLL is built in the same directory as the headers to let CMake find them together through PATH:

    cd <qtkeychain Clone Dir>
    cmake -G "MinGW Makefiles" .
    cd ..
  1. Create the build directory:

    mkdir client-build
    cd client-build
  1. Build the client:

    cmake -G "MinGW Makefiles" -DNO_SHIBBOLETH=1 ../client

    You can try using ninja to build in parallel using cmake -G Ninja ../client and ninja instead. Refer to the generic build instructions section for additional options. The ownCloud binary will appear in the bin directory.

Windows Installer Build (Cross-Compile)

Due to the large number of dependencies, building the client installer for Windows is currently only officially supported on openSUSE, by using the MinGW cross compiler. You can set up any currently supported version of openSUSE in a virtual machine if you do not have it installed already.

In order to make setup simple, you can use the provided Dockerfile to build your own image.

  1. Assuming you are in the root of the ownCloud Client’s source tree, you can build an image from this Dockerfile like this:

    cd admin/win/docker
    docker build . -t owncloud-client-win32:<version>

    Replace <version> by the version of the client you are building, e.g., for the release of the client that this document describes. If you do not wish to use docker, you can run the commands in RUN manually in a shell, e.g., to create your own build environment in a virtual machine.

    Docker images are specific to releases. Newer releases may have different dependencies, and thus require a later version of the docker image! Always pick the docker image fitting your release of ownCloud client!

  1. From within the source tree Run the docker instance:

    docker run -v "$PWD:/home/user/client" owncloud-client-win32:<version> \
       /home/user/client/admin/win/docker/ client/  $(id -u)

    It will run the build, create an NSIS based installer, as well as run tests. You will find the resulting binary in an newly created build-win32 subfolder.

    If you do not wish to use docker, and ran the RUN commands above in a virtual machine, you can run the indented commands in the lower section of manually in your source tree.

  1. Finally, you should sign the installer to avoid warnings upon installation. This requires a Microsoft Authenticode Certificate osslsigncode to sign the installer:

    osslsigncode -pkcs12 $HOME/.codesign/packages.pfx -h sha256 \
        -pass yourpass \
        -n "ACME Client" \
        -i "" \
        -ts "http://timestamp.server/" \
        -in ${unsigned_file} \
        -out ${installer_file}

    For -in, use the URL to the time stamping server provided by your CA along with the Authenticode certificate. Alternatively, you may use the official Microsoft signtool utility on Microsoft Windows.

If you’re familiar with Docker, you can use the version of osslsigncode that is part of the docker image.

Generic Build Instructions

To build the most up-to-date version of the client:

  1. Clone the latest versions of the client from Git as follows:

    git clone git://
    cd client
    # master this default, but you can also check out a tag like v2.4.1
    git checkout master
    git submodule init
    git submodule update
  1. Create the build directory:

    mkdir client-build
    cd client-build
  1. Configure the client build:

    cmake -DCMAKE_PREFIX_PATH=/opt/ownCloud/qt-5.10.1 -DCMAKE_INSTALL_PREFIX=/Users/path/to/client/../install/  -DNO_SHIBBOLETH=1 ..

    For Linux builds (using QT5 libraries via build-dep) a typical setting is -DCMAKE_PREFIX_PATH=/opt/ownCloud/qt-5.10.1/ - version number may vary. For Linux builds using system dependencies -DCMAKE_PREFIX_PATH is not needed. You must use absolute paths for the include and library directories.

    On Mac OS X, you need to specify -DCMAKE_INSTALL_PREFIX=target, where target is a private location, i.e. in parallel to your build dir by specifying ../install.

    qtkeychain must be compiled with the same prefix e.g., -DCMAKE_INSTALL_PREFIX=/Users/path/to/client/../install/

  1. Call make. The ownCloud binary will appear in the bin directory.

  1. (Optional) Call make install to install the client to the /usr/local/bin directory. The following are known CMake parameters:

    • QTKEYCHAIN_LIBRARY=/path/to/qtkeychain.dylib -DQTKEYCHAIN_INCLUDE_DIR=/path/to/qtkeychain/ Used for stored credentials. When compiling with Qt5, the library is called qt5keychain.dylib. You need to compile QtKeychain with the same Qt version. If you install QtKeychain into the CMAKE_PREFIX_PATH then you don’t need to specify the path manually.

    • WITH_DOC=TRUE: Creates doc and manpages through running make; also adds install statements, providing the ability to install using make install.

    • CMAKE_PREFIX_PATH=/path/to/Qt5.10.1/5.10.1/yourarch/lib/cmake/: Builds using that Qt version.

    • CMAKE_INSTALL_PREFIX=path: Set an install prefix. This is mandatory on Mac OS