Compiling KDE – Fedora: Dependencies
As promised in the previous post, I started compiling KDE from svn, using again kdesvn-build script. Without further saying, I present you, ladies and gentlemen, the list of deps:
KDESUPPORT
avahi-devel
boost-devel
cmake
cups-devel
qt-devel
svn
make
raptor-devel
redland-devel
postgresql-libs
clucene-core-devel
gcc-c++
bzip2-devel
libxml2-devel
expat-devel
xine-lib-devel
gstreamer-devel
glib2-devel
dbus-devel
cppunit-devel
hyperestraier-devel
KDELIBS
pcre-devel
libxslt-devel
giflib-devel
KDEPIMLIBS
gpgme-devel
libical-devel
KDEBASE
libXcomposite-devel
libXdamage-devel
libXtst-devel
alsa-lib-devel
PyQt4
libxklavier-devel
xmms-devel
libsmbclient-devel
libusb-devel
lm_sensors-devel
OpenEXR-devel
pulseaudio-libs-devel
pciutils-devel
libxkbfile-devel
KDENETWORK
libidn-devel
qca-ossl
I’m sure you have noticed some different packages like redland and raptor, this time, instead of installing soprano-devel or strigi-devel, I installed their deps. Just another way to do it.
P.S. Just for the fun of it, this time I didn’t use kdesvn-build and built everything into /usr. I will write another post on how to compile KDE manually without any kind of script. Then you can write your own script to make it even easier to update it! 
And, you have more control over what actually happens!
Building KDE from svn: running your build
After you build KDE from svn, you won’t see it in the Login manager (because there are .desktop files created for it), so you have to run it manually! How to do it is easy as ummmm….pick a name
Only thing you do is that you should add your kde binary files to your PATH. To do this, open ~/.bashrc and add these lines to it (before the last line):
export PATH=/home/$USER/kde/bin:$PATH
and replace $USER with your username, say “John” (without quotes)
Now, logout, and when you are in Login screen, press Alt+Ctrl+1 (or 2, or 3, up to 6).
You’ll be greeted with a black and deadly screen (it’s not so deadly, believe me). Now in there, login as yourself. It asks you for your username and password. After you enter them, you will go to a normal prompt just as when you open up a terminal. Now type:
$ xinit -- :1
You just started an X server. One which you can start your kde into.
You have now a terminal in from of you. To start kde, just type:
$ ./kde/bin/startkde
and live happily ever after 
Welcome to the latest KDE build EVER!!
for logging out, just close the terminal, then you will go back to the prompt, then press Ctrl+Alt+7 to get back to the login manager.
Building KDE from svn: using kdesvn-build
There are some things you have to be aware of when compiling KDE from svn with kdesvn-build. There has been some problems that I encountered when compiling kde, but I don’t clearly remember them, so I will suffice to the solution for now:
To use the current strigi library (the one you manually compiled with kdesupport), do this in the terminal:
$ export STRIGI_HOME=/home/$USER/kde/
remember that you have to do it after you have compiled kdesupport.
When building kdebase, make sure you remove soprano-devel. kdebase will mistakenly use the old soprano-devel rather than the one compiled with kdesupport.
Building KDE from svn: dependencies
So here is the list of dependencies I promised in the previous post:
OpenSUSE
alsa-devel
automoc4
avahi-devel
boost-devel
cmake
patch --> qt-copy
cups-devel
giflib-devel
kde4-filesystem
libQtWebKit-devel
libakonadiprotocolinternals-devel
libgpgme-devel
libqimageblitz-devel
libqt4-devel
libsmbclient-devel
libsoprano-devel
libtiff-devel
libxslt-devel
phonon-devel
shared-mime-info
strigi-devel
xine-devel
svn
make
libbz2-devel
hal-devel
avahi-compat-mDNSResponder-devel
mysql-devel
libjasper-devel
libical-devel
Yes, I compiled (am compiling right now, kdebase and it’s 94%) kde on OpenSUSE just for fun! I’ll play with OpenSUSE a little bit until F10 comes out, and then I’ll be back to my beloved Fedora!!
Note that this list is for OpenSuse, BUT, the deps are the same for almost every other distro. Therefore, with a little bit changing the names according to your distros package naming conventions, you can get the same stuff. For example, in Fedora, libsoprano-devel would be soprano-devel and libQtWebKit-devel should be something like QtWebKit-devel.
Being on the edge
I’m trying again to build KDE4 from svn. This time, I will use kdesvn-build. I have done it before, successfully, on OpenSuse, but this time I want to do it on Fedora. Right now it’s downloading the sources. What I really wanted to do, in fact, was that I wanted to make a complete list of dependencies for building KDE4 from scratch. I freshly installed F9 on my laptop and without updating nor installing anything, I download kdesvn-build script and install svn and gcc-c++. Now one by one, whenever it fails, I look at the logs and find out what is missing. So far, I need patch and cmake. Stay updated as I will post the list of deps as soon as they are available
