Difference between revisions of "Getting Started/Build/Environment"

Jump to: navigation, search
(Environment Configuration)
(Sample .build-config file)
Line 113: Line 113:
# The default values provided are for a master/trunk/unstable build in your own
# The default values provided are for a master/trunk/unstable build in your own
# user directory using your own build of Qt
# user directory using your system Qt
# Uncomment if building on a 64 bit system
# Uncomment if building on a 64 bit system

Revision as of 10:54, 21 March 2011



Configuring your build environment is the single most important step in building KDE. A wrong decision or mistake here could at best mean you have to rebuild everything from scratch again, or at worst break your system KDE rendering your system unusable.

A lot of very important concepts will be discussed and it is important that you understand them before proceeding.

A set of configuration scripts and bash commands are provided as a recommended configuration when building KDE manually. If you use these as provided then your KDE build will be a lot easier and it will be easier for you to find support online. The one disadvantage to these scripts is that they hide important details from you which you may want to learn about, but the two methods are completely interchangeable so once you are comfortable building KDE using the scripts you can learn more by doing everything yourself.

It is recommended that you build KDE using your normal user account. In some circumstances you may want to build using a separate user account, such as if you are a KWin or Plasma developer wishing to test a full KDE session with compositing effects, but for most circumstances a simple way can be found for achieving the same aim while still running using your normal user account (e.g. Nested X using xypher).

Git Configuration

KDE uses Git as its main source repository and revision control software which you need to configure before you can use it in KDE. You can find the recommended Git configuration for KDE on the Git Configuration page.

Path Configuration

This section explains the different paths that need to be configured for building KDE. The following section will demonstrate a simple method for setting up the required paths.

Source Path

The $KDE_SRC path environment variable defines where the KDE Build System can find the source files.

TODO: Decide how to do stable and unstable source branches in parallel. While Git supports having these in a single source clone to save disk space, it is sometimes nice to have separate clones to allow simultaneous parallel builds, and it takes less scripting to achieve. It's also conceptually closer to how svn works so seems preferable during the transition.

Build Path

The $KDE_BUILD path environment variable defines where the KDE Build System will create the build files.

The KDE build system requires that your source and build files be in different directories (aka out-of-source builds). This keeps your source directories clean and simplifies management of your different build files. :

  • It makes it very easy to rebuild from scratch, you just delete the build directory to remove all the generated files - even old ones that "make clean" wouldn't remove.
  • It is easier to look at the source files (grep, ls etc.).
  • It allows multiple build trees with different settings, e.g. debug and release.

While for some simple build scenarios you could just create a "build" directory inside your 'source' directory (e.g. "kde/src/kdelibs/build"), this negates many of the advantages when used with a full KDE build. Instead clearly separate paths are recommended.

For example if we were building kdelibs we could have the following folders:


If you plan to build multiple branches of KDE such as stable and unstable in parallel then you will need to add an extra level to the directory:


Install Path

The $KDEDIR path environment variable defines where the KDE Build System will install KDE.

It is strongly recommended for a development build that you do a user based install and not a root install, i.e. install your KDE build into a user-owned directory and not into the system /usr directory. This provides a number of advantages:

  • Your root/system installed version of KDE is untouched, meaning your normal desktop and applications remain stable and usable even if your development build breaks
  • You can build and run multiple development versions of KDE at the same time, i.e. a stable branch for bug fixes and an unstable branch for new features
  • You can use a single alias or bash command to compile/link/install without having to do a su/sudo in the middle
  • Doing "make" and "make install" as the same user is a lot quicker as the Makefiles are only parsed once.
  • No root owned files in the build directory
  • No problems caused by root not having a correctly configured KDE build environment
  • It makes it very easy to reinstall from scratch, you just delete the install directory to remove all the installed files and rerun the build.

That said, the build instructions provided are completely generic and will work for building a root system install if you configure your environment to do so, i.e. for Linux from Scratch or doing a root install in a virtual machine for testing or packaging purposes.

For the kdelibs example given above we would then have:


Home Path

The $KDEHOME path environment variable defines wat directory KDE will treat as your home folder, i.e. for stroing data writing config files to.

For the same reason as the Install Path, it is strongly recommended that you set your KDE Home Path to be different from your normal home folder.

For the kdelibs example given above we would then have:


XDG Data Paths

The Cross Desktop (XDG) Data Paths are a standard set of paths used to find various shared cross-desktop standard data such as mimetypes. If you are building the KDE Development Platform yourself then it is recommended to block these paths from seeing your system install (usually /usr) as this will cause problems. However, if you do so you must install the shared-mime-info data into your development install path. If you are not building your own KDE Development Platform then you should not override the XDG Data Paths.

Other Paths

There are a number of other paths that are required, but these can all be automatically derived and created by the config script given below.

Environment Configuration

The example environment configuration script given below is for building KDE against your system Qt under your normal user account with an out-of-source build and installing into a user directory. By changing just four variables you can use the script to configure any KDE build environment you want.

It is recommended you create a separate script for each build environment you require. If you have separate source directories for each build then save the script into the root source directory with the name ".build-config" to allow the bash scripts in the next section to automatically load the config and create the required directories.

If you don't wish to use the bash scripts then you must manually create the required directories and manually execute the config script.

If you are building KDE using a dedicated user to run a full desktop session, then you should put this config into the users ~/.bashrc file.

Please see the notes above about the XDG Data Paths, the example config script below overrides the XDG Data Paths.

Sample .build-config file

  1. KDE4 Build Environment configuration script
  2. To configure your build environment set LIB_SUFFIX, BASEDIR, BUILDNAME and
  3. QTDIR as appropriate
  4. The default values provided are for a master/trunk/unstable build in your own
  5. user directory using your system Qt
  1. Uncomment if building on a 64 bit system
  2. export LIB_SUFFIX=64
  1. Set where your base KDE development folder is located, usually ~/kde

export BASEDIR=~/kde

  1. Give the build a name, e.g. master, 4.6, debug, etc

export BUILDNAME=master

  1. Set up which Qt to use
  2. Use the system Qt, adjust path as required

export QTDIR=/usr

  1. Uncomment to use your own build of qt-kde
  2. export QTDIR=$BASEDIR/inst/master/qt-kde
  3. export PATH=$QTDIR/bin:$PATH
  1. Set up the KDE paths


  1. Add the KDE plugins to the Qt plugins path

export QT_PLUGIN_PATH=$KDEDIR/lib/kde4/plugins

  1. Do we really need these?

export KDE4_DBUS_INTERFACES_DIR=$KDEDIR/share/dbus-1/interfaces export PYTHON_SITE_PACKAGES_DIR=$KDEDIR/lib/python2.6/site-packages/PyKDE4

  1. Export the standard paths to include KDE


  1. Export the CMake paths so it searches for KDE in the right places


  1. Unset XDG to avoid seeing KDE files from /usr
  2. If unset then you must install shared-mime-info


  1. Uncomment if you are using Icecream for distributed compiling
  2. export PATH=/opt/icecream/bin:$PATH
  1. Report what the environment is set to

echo echo "*** Configured KDE Build Environment " $BUILDNAME " ***" echo echo "QTDIR=" $QTDIR echo "KDEDIR=" $KDEDIR echo "PATH=" $PATH echo

Useful Bash Scripts

This section provides a set of bash scripts to simplify setting up your build environment and managing the KDE build process. If you use these scripts, then you can use the 'Easy Recipe' option documented in these pages. If you do not want to use these scripts then you will need to use the 'Full Recipe' option documented in these pages.

You can find further details about using these scripts on the Build Recipes page.

The main commands provided are:


Change to source directory


Change to build directory


Configure, build and install the current KDE module


Save this script in an executable file called "findup" somewhere in your path, usually ~/bin/findup.

  1. !/bin/sh

arg="$1" if test -z "$arg"; then exit 1; fi

while ! test -f "$arg"; do

cd ..
if test "$PWD" = "/"; then
   exit 1


echo $PWD/$arg


Add the following script to the end of your ~/.bashrc, or save as a separate ~/.kde-bashrc and add source .kde-bashrc to your ~/.bashrc.

    1. A script to setup some needed variables and functions for KDE 4 development.
    2. This should normally go in the ~/.bashrc file of your kde development user.

prepend() { [ -d "$2" ] && eval $1=\"$2\$\{$1:+':'\$$1\}\" && export $1 ; }

  1. This will make the debug output prettier


  1. Make
  2. Tell many scripts how to switch from source dir to build dir:


  1. Use makeobj instead of make, to automatically switch to the build dir.
  2. If you don't have makeobj, install the package named kdesdk-scripts or
  3. kdesdk, or check out kdesdk/scripts from svn, or just don't set the alias
  4. yet.

alias make=makeobj

  1. A function to easily build the current directory of KDE.
  2. This builds only the sources in the current ~/{src,build}/KDE subdirectory.
  3. Usage: cs KDE/kdebase && cmakekde
  4. will build/rebuild the sources in ~/src/KDE/kdebase

function cmakekde {

   if test -n "$1"; then
       # srcFolder is defined via command line argument
       # get srcFolder for current dir
       srcFolder=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
   # we are in the src folder, change to build directory
   # Alternatively, we could just use makeobj in the commands below...
   if [ "$srcFolder" = "$current" ]; then
   # To disable tests, remove -DKDE4_BUILD_TESTS=TRUE
   # To save disk space change "debugfull" to "debug"
   cmake "$srcFolder" \
       # Comment out the following two lines to stop builds waiting after
       # the configuration step, so that the user can check configure output
       echo "Press <ENTER> to continue..."
       read userinput
       # Note: To speed up compiling, change 'make -j2' to 'make -jx',
       #   where x is your number of processors +1
       nice make -j2 && make install
       #Use this line instead if using icecream
       #nice make CC=icecc -j6 && make install
       return ${RETURN}


function cd() {

 if test -z "$1"; then
   builtin cd
 elif test -z "$2"; then
   builtin cd "$1"
   builtin cd "$1" "$2"
 _f=`findup .build-config`
 if test -n "$_f" -a "$_lastf" != "$_f"; then
   echo "Loading $_f"
   source "$_f"


  1. A function to easily change to the build directory.
  2. Usage: cb KDE/kdebase
  3. will change to $KDE_BUILD/KDE/kdebase
  4. Usage: cb
  5. will simply go to the build folder if you are currently in a src folder
  6. Example:
  7. $ pwd
  8. /home/user/src/KDE/kdebase
  9. $ cb && pwd
  10. /home/user/build/KDE/kdebase

function cb {

       local dest
   # Make sure build directory exists.
   mkdir -p "$KDE_BUILD"
   # command line argument
   if test -n "$1"; then
       cd "$KDE_BUILD/$1"
   # substitute src dir with build dir
   dest=`pwd | sed -e s,$KDE_SRC,$KDE_BUILD,`
   if test ! -d "$dest"; then
       # build directory does not exist, create
       mkdir -p "$dest"
   cd "$dest"


  1. Change to the source directory. Same as cb, except this
  2. switches to $KDE_SRC instead of $KDE_BUILD.
  3. Usage: cs KDE/kdebase
  4. will change to $KDE_SRC/KDE/kdebase
  5. Usage: cs
  6. will simply go to the source folder if you are currently in a build folder
  7. Example:
  8. $ pwd
  9. /home/myuser/kde/build/master/KDE/kdebase
  10. $ cs && pwd
  11. /home/myuser/kde/src/master/KDE/kdebase

function cs {

       local dest current
   # Make sure source directory exists.
   mkdir -p "$KDE_SRC"
   # command line argument
   if test -n "$1"; then
       cd "$KDE_SRC/$1"
       # substitute build dir with src dir
       dest=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
       if [ "$dest" = "$current" ]; then
           cd "$KDE_SRC"
           cd "$dest"


  1. Add autocompletion to cs function

function _cs_scandir {

       local base ext
   if [ -d $base ]; then
       for d in `ls $base`; do
           if [ -d $base/$d ]; then
               dirs="$dirs $ext$d/"


function _cs() {

   local cur dirs
   _cs_scandir "$KDE_SRC"
   _cs_scandir "$KDE_SRC/KDE" "KDE/"
   COMPREPLY=( $(compgen -W "${dirs}" -- ${cur}) )


complete -F _cs cs

svndiff () {

   svn diff "$*" | colordiff | less;


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal