Wed Dec 23, 2009 2:09 pm
In this tutorial, I describe how to build kde trunk on ArchLinux, using several tools, and providing you with configuration. This is a tutorial for KDE developers (or those who want to become a KDE developer), not for end users.
I decided I want the KDE trunk to be built in it’s own “sandbox”, meaning in a completely closed environment, but not in a virtual environment /vmware / xen / kvm or anything similar. This is done using a chroot, with basically a 2nd ArchLinux installation on your machine.
I do this for one simple reason, it is possible that you need more recent libraries for the kde trunk, and you may not want to mess up your system with other unstable libraries. You of course could also build and install unstable libraries into your home directory, but I like a closed environment better. Also, there have been problems installing kde to a custom directory lately, due to plasmascripts.py which is part of kdebase-workspace. To avoid this troubles, and even being able to push kde to /usr, I decided for a chroot.
Also, you’re able to do this on machines where you don’t even have root access, even though, you’ll have to change a few parts on the tutorial.
All this boils down to install Arch stable for your private use on your main installation, and a Arch “sandbox” in a chroot.
First Step – chroot environment
NOTE: If you do not want to run KDE trunk in a sandbox, just skip this chapter. You may need to change some of the commands lateron, as when starting Xephyr.
There is a great guide how to set up a chroot in Arch in the Arch Linux wiki. It is basically described how to build a Arch32 chroot in Arch64, but with some simple modifications you can also build a Arch64 chroot in Arch64. I’ll anyway describe here how to do it, if it doesn’t work out for you, you may want to read the guide. You’ll find the link in the Ressources section of this tutorial.
First of all, you can set up your arch chroot in any directory, and it must not be /opt, as in my case. This can depend on your partition settings – how ever you like.
There is a rc-script which is used to start the Arch chroot. You can add this to your rc.conf if you like.
You can save this file to /etc/rc.d/arch-chroot
You can also download it from >here<
As the next step, you must chmod the file to be executable, and you should enter your chroot.
Installing the KDE build dependencies
Setting up your KDE Development user
This step is important. You may not want to crash your local kde user and ~/.kde4 or ~/.kde directory. Since this needs environment variables, as well as your KDE install will need them, we create a own user for this.
Make sure your user is added to all groups you need for kde development, in example if you need sound or device plugging. This example includes my current configuration.
Next, you should edit your ~/.bashrc
Add the following pathes and settings. This must be local user settings, if you use ksh or another shell for your user, make sure this settings work!
kdesvn-build is a tool compiling and installing the KDE trunk (or other) repositories, this will easen up things a lot.
kdesvn-build must be configured properly. I provide my current configuration for you to download >here<
The configuration should work out of the box, I’ll describe shortly some of the options I edited.
First of all, the qt-kde git repository is fetched by http, because kdesvn-build has problems with git urls for some unknown reasons.
Also, you currently need to build phonon first form the qt repository, and then from the kdesupport library. I don’t really know why, maybe has to do with the qmake configuration parameters available building qt with phonon. This trick comes from Thiago Macieira, some KDE users on #kde-devel in IRC told me about that it’s currently needed.
Now, you should download the latest kdesvn-build from the official kdesvn-build page, extract it, and copy the kdesvn-build file in the user directory of the kde-devel user.
After you have this, kdesvn-build directory should include kdesvn-build and .kdesvn-buildrc
Now, run kdesvn-build, and ensure that you include the option –no-snapshots the first time you run it. This has the reason that kdesvn-build prefers snapshots on the first checkout, updating just a few files later. The problem is, that the svn snapshots of kde are broken (in example taglib/admin is fetched of 3.5 branch, which is just one of a lot of problems in the -svn snapshots I stumbled over).
Also note, that kdesvn-build obviously has problems building kde to /usr and qt to a custom directory at the same time. I talked Michael Pyne (maintainer of kdesvn-build) about this, but decided I will try to fix the bug myself, due to the reason that I can reproduce the problem. The version at the time writing (1.11) is still broken.
Afterwards, your ~/ direcotry should look like this:
Running kde trunk using Xephyr
Xephyr is a tool for nested sessions which shipping with the XOrg server. In archlinux the package xorg-server includes Xephyr, which was installed in the first chapter.
Switch into your chroot, and start Xephyr (and dbus, you'll need dbus for kde starting up):
You could also use a script to do this for you, and put it into your PATH (/bin/sbin) in your chroot environment:
Start your KDE session
If you’re using evdev, you’ll very likely experience problems with your default keyboard layout and keymappings in Xephyr, since Xephyr uses XKB.
Now, there’s a simple workaround for this, run as user (in example on your primary system with your primary user)
Now autostart xmodmap when your kde4 session starts:
Now, make the file executable
ArchLinux Wiki (Arch32 chroot on Arch64)
KDE Techbase (Getting Started/Build/KDE4)
KDE Techbase (Getting Started/Increased productivity in KDE4 with Scripts)
KDE Techbase (Getting Started/Build/KDE4/ArchLinux)
KDE Techbase (Getting Started/Set up KDE4 for development)
Last edited by STiAT on Sun Jan 10, 2010 6:35 pm, edited 3 times in total.
Thu Dec 24, 2009 1:21 pm
2009-12-24: Updated for kdesvn-build 1.11 (qt-copy options, replaced -qtdbus with -dbus and removed -no-exceptions)
2010-01-01: Fixed arch-chroot section.
2010-01-10:Added dbus bind, so KDE can use the system DBUS.
NOTE: For KDE Sound / Hardware development, you'll need to build and run it in your main environment, to be able to access HAL correctly (you can use Xephyr to start KDE though).
I'll add a tutorial about "how to build KDE in your main environment" lateron, it's basically this tutorial with a few adoptions.