|These pages are currently being completely re-written to reflect the new KDE infrastructure and may not be in a consistent state. Information and commands on some page may no longer be valid and should be used with care.|
Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
This page provides an overview of the KDE build process.
The build process described in these pages is kept as simple and generic as possible, but it is generally assumed you are building KDE4 on Linux. Extra information about building KDE Software on specific distributions or platforms, or certain conditions can be found at the following links:
This section will briefly explain the concepts and steps involved in building software so you are not being asked to blindly follow some recipes you do not understand.
It is assumed you are at least familiar with the basics of using the command line.
The Source step is obtaining a local copy of the source code that you want to build. There are 3 main ways of doing this:
For developing on the unstable branch of the KDE SC it is recommended you Clone or Checkout the required repositories.
Note that Checkout has a different meaning in Git than it does in Subversion.
The following example recipe shows the sequence of commands you would need to enter into the command line to build a typical KDE module:
cd ~/kde-devel/src git clone http://anongit.kde.org/kdelibs.git mkdir ~/kde-devel/build/kdelibs cd ~/kde-devel/build/kdelibs cmake ~/kde-devel/src/kdelibs \ -DCMAKE_BUILD_TYPE=debugfull \ -DCMAKE_INSTALL_PREFIX=$KDEDIR make make install
Let's break that recipe down and explain each step.
First you navigate to a convenient folder to save the code in:
Then request a copy of the code from the KDE source repository, in this example a copy of kdelibs from Git:
git clone http://anongit.kde.org/kdelibs.git
This may take some time to process. For Git you will see out output similar to:
myuser@mybox:~/kde-devel/src> git clone http://anongit.kde.org/kdelibs.git http://anongit.kde.org/kdelibs.git Initialized empty Git repository in /home/myuser/kde-devel/src/kdelibs/.git/ remote: Counting objects: 722134, done. remote: Compressing objects: 100% (138759/138759), done. remote: Total 722134 (delta 586243), reused 715797 (delta 580373) Receiving objects: 100% (722134/722134), 140.90 MiB | 706 KiB/s, done. Resolving deltas: 100% (586243/586243), done. myuser@mybox:~/kde-devel/src>
This example will create a folder called ~/kde-devel/src/kdelibs containing all the kdelibs source code and all its history since KDE began.
For an SVN checkout you will instead see output similar to:
myuser@mybox:~/kde-devel/src> svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk A kdesdk/cmake A kdesdk/cmake/samples A kdesdk/cmake/samples/kpager A kdesdk/cmake/samples/kpager/CMakeLists.txt ... A kdesdk/COPYING.LIB U kdesdk Checked out revision 1223739. myuser@mybox:~/kde-devel/src>
First you create a convenient folder to build the code in:
mkdir ~/kde-devel/build/kdelibs cd ~/kde-devel/build/kdelibs
Next you need to run CMake to create the configuration files to be used in the build:
cmake ~/kde-devel/src/kdelibs \ -DCMAKE_BUILD_TYPE=debugfull \ -DKDE4_BUILD_TESTS=TRUE \ -DCMAKE_INSTALL_PREFIX=$KDEDIR
Various options can be passed to CMake to control how a project gets built, but these are the most common:
The easiest way to build the KDE SC from scratch is to use one of the build scripts that are available. This approach is highly recommended for those new to building KDE SC as it takes care of the Source, Configure, Build, Install and Update steps for you. The builds remain compatible with the manual methods of building KDE SC so you can change later if you want.
Manually building KDE Software requires that you first set up the build environment and install the required development tools and libraries.
This section still to be updated, in the meantime you can obtain some needed steps from the following pages:
Compile and Linking errors are frequent sources of discouragement. Make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. Please read the instructions carefully.
Please review your logs and do searches for fixes. If you cannot find a solution, try the Troubleshooting page. If you still cannot resolve the problem then please ask for help on IRC or a Mailing List.