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 | Українська | 简体中文 | 繁體中文
Building KDE using the kdesvn-build tool
Introduction to kdesvn-build
kdesvn-build is a tool to allow users and developers to easily download and build the latest versions of the KDE Software Compilation (KDE SC) from the KDE source code repositories. It automates the following tasks and more:
- Performing the initial checkout.
- Handling updates for modules that are already checked out.
- Setting up the build system for the module.
- Performing the build and install.
- Specifying your CMake options or configure flags (so you don't have to remember them every time).
Why use kdesvn-build?
So why use kdesvn-build? There are several reasons you may like to use it:
- Less manual editing of commands. Instead of having to remember to add the correct options to the cmake command line or configure command, you can setup the options once and then kdesvn-build will use your settings from then on, saving you from wasting time because you forgot to enable a setting.
- Command logging to help debug build failures. kdesvn-build logs all command outputs to a file. This has several advantages:
- When a module fails to build, you already have the error output saved to disk, ready to be viewed and compared with other error messages to aid debugging.
- Quieter output. Even with CMake, the output of Qt or a KDE SC module build can be extensive. kdesvn-build does not show the details of a module build (but will show the progress), instead an overview of the build process is displayed.
- It's just easier. Instead of having to learn how to use the Subversion and git tools, and how to setup a KDE build system, you can specify what modules you want build, where to install them to, and any other options you want and then have kdesvn-build actually do it, even while you're away from the computer or busy doing other things.
- It's easy to step in yourself. kdesvn-build uses a standard source and build directory layout, and calls the same commands you would. So kdesvn-build will not interfere with you performing the build or editing the source yourself if you so choose.
kdesvn-build is fairly easy to install and setup, but you also need to have the right software installed to build KDE SC. The requirements to build KDE SC are available as follows:
- KDE SC 4: KDE 4 Requirements
In addition to those listed requirements, kdesvn-build requires the Perl scripting platform to be installed. It is installed by default with most distributions, and is required to build KDE SC anyways. kdesvn-build requires Perl 5.8 or higher.
Download and install kdesvn-build
Once your system is setup to be able to compile the KDE SC, you can download kdesvn-build from its website, kdesvn-build.kde.org. The file you download will contain (at least) the kdesvn-build script and a sample configuration file. Installing kdesvn-build is as simple as saving the file and making it executable. If you'd like, you can move it to a directory in your PATH, however for this example we'll put it into the KDE source directory that we use (~/kdesvn)
mkdir -p ~/kdesvn
tar xjvf ~/path/to/kdesvn-build-1.10.tar.bz2
cp kdesvn-build-1.10/kdesvn-build .
Alternatively, the newest kdesvn-build script (and sample config file) can be pulled directly from svn:
mkdir -p ~/kdesvn
svn cat $SVN_ROOT/trunk/KDE/kdesdk/scripts/kdesvn-build > kdesvn-build
svn cat $SVN_ROOT/trunk/KDE/kdesdk/scripts/kdesvn-buildrc-sample > ~/.kdesvn-buildrc
chmod +x kdesvn-build
Setup the configuration
Now you should setup your configuration. For the most part the defaults in the included kdesvn-buildrc-sample should be sufficient.
cp ~/kdesvn/kdesvn-build-1.10/kdesvn-buildrc-sample ~/.kdesvn-buildrc
- Now edit the ~/.kdesvn-buildrc
Also, make sure that the modules you'll want to build are included. You'll want the following at the least:
- qt-copy, kdesupport, kdelibs, kdepimlibs, kdebase
Modules are built in the order they appear in your ~/.kdesvn-buildrc, so the first module should be qt-copy, kdelibs should be before any other KDE SC module, and so on.
You may want to enable the make-install-prefix option if you are installing KDE SC or Qt to a directory that is not in your home directory. make-install-prefix allows you to run su or sudo during the make install process so you can install files as root, or set certain programs to execute with higher permissions (This is required for certain programs to execute properly).
module kdelibs make-install-prefix sudo -S # sudo with no stdin end module module kdebase make-install-prefix sudo -S end module
If a module you'd like to build isn't already present, simply add
module <module-name> end module
at the end of the ~/.kdesvn-buildrc. <module-name> would be whatever the module is called in the software repository (for instance, kdemultimedia).
Useful kdesvn-build commands
kdesvn-build is driven from the command line, so here's a guide to some of the more useful command line options:
|--pretend (Short form -p)||This option is like a dry run. kdesvn-build will process the options and its configuration like normal, and run through the build as normal, but instead of downloading or running the build will instead output what kdesvn-build would have done. You should always run with -p before running kdesvn-build to make sure it is doing what you expect.|
|--no-svn (Alt. form --no-src)||This option skips the source code update step. This is useful if you're running kdesvn-build again soon after the last update and don't want to wait to find out there were no changes.|
|--refresh-build||This option causes kdesvn-build to delete the current build information for the given modules and start building them again from scratch. This option takes a lot of time but gives the best chance of a successful build.|
Any other non-option arguments on the command line are assumed to be modules to build (and are built in the order provided on the command line). If no modules are specified, all of the modules listed in the ~/.kdesvn-buildrc are built in the order listed in the file.
We're almost there. If you're happy with your settings then it's time to test out kdesvn-build. In theory things are as simple as running kdesvn-build and then coming back later. ;)
You may want to test by building qt-copy first however.
If the build failed (kdesvn-build will error out with a nice bright red error message) then there are several possibilities:
- You are missing a key piece of required software (such as a development library)
- The KDE SC code being compiled is broken in some fashion to where it won't build. This is commonly due to newly committed code that worked on the developer's machine, or occasionally on Mondays (when incompatible changes are permitted to kdelibs).
- kdesvn-build is not setup properly. You may be trying to install to a directory that you have no permissions to access for instance, or you may have specified a system qtdir that does not exist.
- The module may depend on a newer version of qt-copy or kdelibs (or other module). In this case you'll have to run kdesvn-build to update the out-of-date module first.
How do you find out what the error was? The output of the failing command will be in the log directory. By default, all log output is in the log subdirectory of the KDE SC source directory. The log directory is laid out like this: log/date-run/module/output-file.log. To simplify finding the appropriate file, there are a couple of symlinks created:
log/latest always has the debugging output for the last time kdesvn-build was run (--pretend doesn't count toward this) log/latest/<module>/error.log has the debugging output for the command that caused a module build to fail.
For instance if qt-copy just failed to build you could read the output like this:
Replace kwrite with your preferred editor. Hopefully the output can guide you to resolving the problem. For instance, if the failure is a cmake output saying you're missing a library, install that library and try again. ;) For link errors you can try running a --refresh-build on the module (or if that doesn't work, required libraries like qt-copy and kdelibs).
If you're stumped by the error you may want to wait a day and try updating again, and hope that the reason for the error has been fixed. You can also try mailing the kde-devel mailing list to see if others know about the problem or have had similar issues.
Assuming you got enough of the modules to build and install to have a working KDE installation, you'll still need to setup your environment correctly to run it. kdesvn-build doesn't help you out here (yet), but the instructions at the .bashrc wiki page apply just as well, except that you'll need to set the environment variables to the settings that are in your ~/.kdesvn-buildrc.
For the KDEDIRS and KDEDIR variable use the setting of the "prefix" option (in the global section). For the QTDIR variable use the setting of the "qtdir" option.
Once your .bashrc is setup logout and log back in again and then you should be able to run your new KDE installation.
Keeping KDE up to date
Keeping your KDE installation up to date is as simple as running kdesvn-build again. Every kdesvn-build has these phases:
- Update the source code for all modules being built.
- Build and then install all the modules.
Old build directories are not deleted by default, so the build after a small update will not normally take as long as the initial build of a module. This is called "incremental make". However it may be necessary at times to perform a full rebuild due to inconsistencies between the build directory configuation and changes to the source directory. You can use the --refresh-build option to force a full rebuild.
For more information on how to take advantage of kdesvn-build, see the online documentation for kdesvn-build, which describes all of the module options and command line options available for kdesvn-build and gives tips on how to perform various useful tasks.
If you have any questions that are not answered please feel free to add them under the Discussion entry for this page and hopefully someone will be able to get the answer.