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: 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.