Getting Started/Build: Difference between revisions
Line 31: | Line 31: | ||
=== Example Recipe === | === Example Recipe === | ||
The following recipe shows the sequence of commands you would need to | 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 | cd ~/kde-devel/src | ||
Line 43: | Line 43: | ||
make install | make install | ||
Let's break that recipe down and explain each step. | |||
Checkout | ==== Checkout Example ==== | ||
First you navigate to a convenient folder to save the code in: | First you navigate to a convenient folder to save the code in: | ||
Line 54: | Line 54: | ||
This may take some time to process. For Git you will see out output similar to: | 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 | http://anongit.kde.org/kdelibs.git | ||
Initialized empty Git repository in | Initialized empty Git repository in /home/myuser/kde-devel/src/kdelibs/.git/ | ||
remote: Counting objects: 722134, done. | remote: Counting objects: 722134, done. | ||
remote: Compressing objects: 100% (138759/138759), done. | remote: Compressing objects: 100% (138759/138759), done. | ||
Line 61: | Line 62: | ||
Receiving objects: 100% (722134/722134), 140.90 MiB | 706 KiB/s, done. | Receiving objects: 100% (722134/722134), 140.90 MiB | 706 KiB/s, done. | ||
Resolving deltas: 100% (586243/586243), 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. | 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: | |||
For SVN you will see output similar to: | |||
myuser@mybox:~/kde-devel/src> svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk | myuser@mybox:~/kde-devel/src> svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk | ||
A kdesdk/cmake | A kdesdk/cmake | ||
Line 77: | Line 78: | ||
myuser@mybox:~/kde-devel/src> | myuser@mybox:~/kde-devel/src> | ||
Configure: | ==== Configure Example ==== | ||
First you create a convenient folder to build the code in: | |||
mkdir ~/kde-devel/build/kdelibs | mkdir ~/kde-devel/build/kdelibs | ||
cd ~/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 \ | cmake ~/kde-devel/src/kdelibs \ | ||
-DCMAKE_BUILD_TYPE=debugfull \ | -DCMAKE_BUILD_TYPE=debugfull \ | ||
-DKDE4_BUILD_TESTS=TRUE \ | |||
-DCMAKE_INSTALL_PREFIX=$KDEDIR | -DCMAKE_INSTALL_PREFIX=$KDEDIR | ||
The first line tells CMake where it can find the source code that is to be built. The second line tells CMake what type of build is required, in this example a debugfull build that will include useful information for when we are debugging any the software. The third line tells CMake we also want the unit tests to be built. The fourth line tells CMake where to install the software. Other options can be passed to CMake to control how a project gets built, but these are the most common. | |||
Build | ==== Build Example ==== | ||
== Scripted Builds == | == Scripted Builds == |
Revision as of 19:22, 4 March 2011
Getting Started/Build
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 | Українська | 简体中文 | 繁體中文
Here you will find instructions for compiling and installing KDE from source and suggestions for when compilation doesn't go so smoothly.
Introduction
Extra Information
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 under specific distributions, platforms or conditions can be found at the following links:
- Building KDE3 or KDE2
- Linux, BSD and other *nix based distributions
- Microsoft Windows
- Apple Mac OS X
- On a Virtual Machine.
Build Basics
This section will briefly explain the steps involved in building software so you understand the concepts 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.
Checkout
The checkout step is obtaining a local copy of the source code that you want to build. While you can download tarball snapshots of the code as at a given time or release to build, it is more common for doing development work to check a copy of the code out directly from the code repository.
Configure
Build
Install
Example Recipe
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.
Checkout Example
First you navigate to a convenient folder to save the code in:
cd ~/kde-devel/src
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>
Configure Example
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
The first line tells CMake where it can find the source code that is to be built. The second line tells CMake what type of build is required, in this example a debugfull build that will include useful information for when we are debugging any the software. The third line tells CMake we also want the unit tests to be built. The fourth line tells CMake where to install the software. Other options can be passed to CMake to control how a project gets built, but these are the most common.
Build Example
Scripted Builds
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 Checkout, Build and Install steps for you. The builds remain compatible with the manual methods of building KDE SC so you can change later if you want.
- The kdesrc-bld script by Michael Pyne
- The build-tool script by Michael Jansen
Getting Ready
Manually building KDE Software requires that you first set up the build environment and install the required development tools and libraries.
- Set up your Build Environment
- Install the Build Requirements
- Install or build Qt
- Install or build kdesupport
Building From Source
Troubleshooting The Build
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.