Guidelines and HOWTOs/Build from source

< Guidelines and HOWTOs
Revision as of 11:38, 5 February 2013 by Jignesh (Talk | contribs) (Qt 5)

Jump to: navigation, search

Build requirements

This section provides information about hard (required) and optional software packages needed to build the KDE Framework.

kdelibs dependencies

  • deb-based distributions (Debian, Ubuntu...): All the dependencies used for the packages can be installed by running
$ apt-get build-dep {packagename}
  • for instance on Ubuntu:
$ sudo apt-get build-dep kdelibs5
  • OpenSuSE: All the dependencies used for building kdelibs can be installed by running:
$ zypper si -d kdelibs5
  • Fedora: All the dependencies used for building kdelibs can be installed by running:
$ yum-builddep kdelibs5


You need CMake for KDE Frameworks 5. If you are already using you can move on to next step else download it from

Alternative for CMake using Git.

  • Choose an install prefix, for instance
 $ export KF5=$HOME/kf5

To avoid repetition of command you can append ~/.bashrc file with above line and execute,

 $ source ~/.bashrc  
  • Checkout and install Latest version of CMake using Git.
 $ git clone git://
 $ cd cmake
 $ ./configure --prefix=$KF5
 $ make
 $ make install

Extra CMake Modules

  • Checkout and build extra-cmake-modules
 $ git clone git://
 $ cd extra-cmake-modules
 $ make 
 $ make install

Qt 5

To build qt5 execute:

 $ git clone git:// --branch dev
 $ cd qt5
 $ git checkout dev
 $ ./init-repository
 $ mkdir build
 $ cd build
 $ ../configure -prefix $KF5 -opensource -confirm-license -nomake examples -qpa -xcb -no-gtkstyle
 $ make
 $ make install

NOTE for ArchLinux users: qtwebkit uses python to generate some files, but it uses python2 syntax. So if you have installed python3, you'll get a compilation error on the file bevause print is no longer a statement, but a function. So, you would like to make /usr/bin/python to point to /usr/bin/python2. See also

Qt5-based dependencies

First, let's setup a "kde:" prefix for git commands. Add the following text to your ~/.gitconfig:

 [url "git://"]
    insteadOf = kde:
 [url "ssh://"]
    pushInsteadOf = kde:

At this point you can continue building things by hand, or download into your source dir, adjust the paths and run kdesrc-build.

To build phonon by hand execute:

 $ git clone kde:phonon --branch phonon4qt5
 $ mkdir phonon/build
 $ cd phonon/build
 $ make
 $ make install

Then build attica (branch master), and strigi (branch master, with submodules) and install them into the same prefix.

To build the patched libdbusmenu-qt execute:

 $ bzr branch lp:libdbusmenu-qt
 $ wget
 $ cd libdbusmenu-qt
 $ patch -p0 -i ../libdbusmenu-qt.diff
 $ mkdir build
 $ cd build
 $ make
 $ make install

Build KDE frameworks

Current state of KDE framework exist in frameworks branch of kdelibs.


 $ git clone kde:kdelibs --branch frameworks
 $ mkdir  kdelibs/build 
 $ cd kdelibs/build 
 $ make
 $ make install

Updating the already built framework. If the source code has been checked from a branch, it is possible to update the source code with newly added changes and build again. Usually only changing parts will be built, so this operation would be faster than building the source code from scratch.

Go to your source directory and execute following commands.

 $ git pull --rebase
 $ cd build
 $ make
 $ make install

Runtime setup

To use your new KF5 install prefix (let's call it $KF5) :

export PATH=$KF5/bin:$PATH
   (lib64 instead of lib, on OpenSUSE and similar)
export QT_PLUGIN_PATH=$KF5/lib/plugins:$QTDIR/plugins:$QT_PLUGIN_PATH
   (lib64 instead of lib, on OpenSUSE and similar)

To use separate user settings for KF5:

export XDG_DATA_HOME=$HOME/.local5
export XDG_CONFIG_HOME=$HOME/.config5
export XDG_CACHE_HOME=$HOME/.cache5

To be able to compile other stuff on top of KF5:


To get more information out of qDebug statements (i.e. make it more like kDebug) :

export QT_MESSAGE_PATTERN='%{appname}(%{pid})/%{category} %{function}: %{message}'

Don't bother with KDEDIR and KDEHOME etc. this stuff isn't used anymore.

Running unit tests

You need a separate DBus session because the dbus server needs to have the right value of XDG_DATA_DIRS, in order to find $KF5/share/dbus-1/services for starting services (e.g. kded5).

eval `dbus-launch`
make test

Warning: never start a KDE4 application in this separate DBus session, it would conflict with your running KDE4 desktop.

Content is available under Creative Commons License SA 4.0 unless otherwise noted.