Getting Started/Build/Recipes - Revision history

Odysseus at 17:13, 25 May 2011

2011-05-25T17:13:02Z

Odysseus at 12:56, 19 March 2011

2011-03-19T12:56:52Z

Odysseus: /* Unstable Git */

2011-03-09T11:43:52Z

‎Unstable Git

Odysseus at 21:25, 7 March 2011

2011-03-07T21:25:47Z

Odysseus at 21:17, 7 March 2011

2011-03-07T21:17:13Z

Odysseus: Created page with '== 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 variat...'

2011-03-07T21:16:15Z

Created page with '== 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 variat...'

New page

== 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 [[Getting_Started/Build/Environment|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>
cmakekde

==== 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>
cmakekde

==== 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>
cmakekde

=== Subversion Unstable ===

cd $KDESRC/master
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/<module>
cd <module>
cmakekde

If you have a developer account the Subversion command will be:
svn checkout svn+ssh://<username>@svn.kde.org/home/kde/trunk/KDE/<module>

=== Subversion Stable ===

cd $KDESRC/<stable-branch>
svn checkout svn://anonsvn.kde.org/home/kde/branches/KDE/<branch>/<module>
cd <module>
cmakekde

If you have a developer account the Subversion command will be:
svn checkout svn+ssh://<username>@svn.kde.org/home/kde/branches/KDE/<branch>/<module>

=== Full Stable Git Recipe ===

cd <your source root directory>
git clone git://anongit.kde.org/<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_INSTALL_PREFIX=$KDEDIR
\ -DCMAKE_BUILD_TYPE=debugfull
\ -DKDE4_BUILD_TESTS=TRUE
nice make -j2 # for faster compiles use -j(X+1)' where X is your number of processor cores
make insta

← Older revision		Revision as of 12:56, 19 March 2011
Line 159:		Line 159:
	If you have a developer account the Subversion command will be:		If you have a developer account the Subversion command will be:
	svn checkout svn+ssh://<username>@svn.kde.org/home/kde/branches/KDE/<branch>/<module>		svn checkout svn+ssh://<username>@svn.kde.org/home/kde/branches/KDE/<branch>/<module>
		+
		+	=== Useful Tips ===
		+
		+	==== make /fast ====
		+
		+	If you want to recompile part of a module without rebuilding any other parts of a module that it uses then you can pass make the /fast option.
		+
		+	For example if you just want to rebuild the contentes of kdelibs/kdeui without rebuilding the contents of kdelibs/kdecore that it uses, then simply do:
		+	make kdeui/fast
		+	make install/fast

@@ Line 68: / Line 68: @@
 === Full Recipe ===
-==== Unstable Git ====
+==== Git Unstable Master ====
 This will be the most commonly used version of the Full Recipe.

@@ Line 22: / Line 22: @@
   git clone kde:<project>.git
   cd <project>
-  cmakekde
+  kdebuild
 ==== Git Unstable Branch ====
@@ Line 31: / Line 31: @@
   git branch --track <branch> origin/<branch>
   git checkout <branch>
-  cmakekde
+  kdebuild
 ==== 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.
+This recipe uses [[/Development/Git/Configuration#Multiple_Work_Branches|git-new-workdir script]] to set up a separate work directory for working on the stable branch.  This will save excessive rebuilding when switching between stable and unstable and uses less space than a separate clone.
 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 $KDE_SRC/<stable-branch>/<module>
+  cd $KDE_SRC/master/<module>
-  git clone kde:<project>.git
+  git-new-workdir <project> $KDE_SRC/<stable-branch>/<module>/<project> <stable-branch>
- cd <project>
+  cd $KDE_SRC/<stable-branch>/<module>/<project>
- git branch --track <stable-branch> origin/<stable-branch>
+  kdebuild
-  git checkout <stable-branch>
-  cmakekde
+An example git-new-workdir command for KDE SC 4.6 would be:
 ==== Subversion Unstable ====
@@ Line 51: / Line 53: @@
   svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/<module>
   cd <module>
-  cmakekde
+  kdebuild
 If you have a developer account the Subversion command will be:
@@ Line 61: / Line 63: @@
   svn checkout svn://anonsvn.kde.org/home/kde/branches/KDE/<branch>/<module>
   cd <module>
-  cmakekde
+  kdebuild
 If you have a developer account the Subversion command will be:
@@ Line 101: / Line 103: @@
 ==== 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.
+This recipe uses [[/Development/Git/Configuration#Multiple_Work_Branches|git-new-workdir script]] to set up a separate work directory for working on the stable branch.  This will save excessive rebuilding when switching between stable and unstable and uses less space than a separate clone.
 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 <your source branch directory>
+  cd $KDE_SRC/master/<module>
- git clone git://anongit.kde.org/<module>.git
+  git-new-workdir <project> $KDE_SRC/<stable-branch>/<module>/<project> <stable-branch>
- cd <project>
-  git branch --track <stable-branch> origin/<stable-branch>
- git checkout <stable-branch>
   cd <your build branch directory, or the module source dir>
   mkdir <your module build dir>
@@ Line 119: / Line 118: @@
   nice make -j2 # for faster compiles use -j(X+1)' where X is your number of processor cores
   make install
 ==== Subversion Unstable ====

@@ Line 45: / Line 45: @@
   cmakekde
-=== Subversion Unstable ===
+==== Subversion Unstable ====
   cd $KDESRC/master
@@ Line 55: / Line 55: @@
   svn checkout svn+ssh://<username>@svn.kde.org/home/kde/trunk/KDE/<module>
-=== Subversion Stable ===
+==== Subversion Stable ====
   cd $KDESRC/<stable-branch>
@@ Line 65: / Line 65: @@
   svn checkout svn+ssh://<username>@svn.kde.org/home/kde/branches/KDE/<branch>/<module>
-=== Full Stable Git Recipe ===
+==== Full Recipe ====
   cd <your source root directory>