Getting Started/Build/Historic/KDE4

Build Recipes

The recipes provided here should be used when following the Build pages for KDE Software. These recipes will not be repeated in the Build pages, only variations from the standard recipe will be documented, usually just the git or svn repository address, but sometimes also additional configuration options.

The Easy Recipe relies on you setting up your environment according to the KDE recommendations. This will give you many shortcuts to save on typing. See the Build Environment section on how to do this.

The Full Recipe is provided for those who wish to control their own build or want to see the full steps required, and don't mind lots of typing.

In Git many KDE Modules have been split up into separate Projects for each Application or Library. Putting all the Git Projects into the same source directory would get very messy. To help keep everything easy to update the recipe recommends you organize the Projects into separate sub-directories for each Module.

For Subversion the repository address changes if you have a developers account or if you want a stable release.

For Git the repository address does not change if you have a developers account or if you want a stable release, you always clone the project from anongit. However a stable build requires some extra steps.

Easy Recipe

Git Unstable Master

This will be the most commonly used version of the Easy Recipe.

cd $KDESRC/master/<module>
git clone kde:<project>.git
cd <project>

Git Unstable Branch

This recipe uses the same Git clone as your main Unstable Master build but allows you to build a specific development branch you may be interested in. It assumes you have already cloned the project repository. Use 'git branch -r' to find out the available development branches.

cd $KDESRC/master/<module>/<project>
git branch --track <branch> origin/<branch>
git checkout <branch>

Git Stable Branch

This recipe creates a new clone of the Project and sets it to use a stable branch. This may be wasteful of disk space if you already have an Unstable clone, but it does allow you to work on Unstable and Stable at the same time without excessive management or rebuilding. It also closely mirrors how Subversion works.

The stable branch name will be of the form 'KDE/4.6' or '4.6' depending on the Project. Use 'git branch -r' to find out the available release branches.

cd $KDESRC/<stable-branch>/<module>
git clone kde:<project>.git
cd <project>
git branch --track <stable-branch> origin/<stable-branch>
git checkout <stable-branch>

Subversion Unstable

cd $KDESRC/master
svn checkout svn://<module>
cd <module>

If you have a developer account the Subversion command will be:

svn checkout svn+ssh://<username><module>

Subversion Stable

cd $KDESRC/<stable-branch>
svn checkout svn://<branch>/<module>
cd <module>

If you have a developer account the Subversion command will be:

svn checkout svn+ssh://<username><branch>/<module>

Full Recipe

Unstable Git

cd <your source root directory>
git clone git://<module>.git
cd <your build root directory, or the module source dir>
mkdir <your module build dir>
cd <your module build dir>
cmake <path to your module source dir>
      \ -DCMAKE_BUILD_TYPE=debugfull
nice make -j2 # for faster compiles use -j(X+1)' where X is your number of processor cores
make insta

This page was last edited on 11 March 2016, at 10:32. Content is available under Creative Commons License SA 4.0 unless otherwise noted.