Difference between revisions of "Getting Started/Build/KDE4"

Jump to: navigation, search
(Set up CMake)
(more in depth .bashrc , removed {{path/...}} in <code>, more visual fixes and some claryfications)
Line 36: Line 36:
 
Switch to the user kde-devel: (the dash also changes to the new home directory)
 
Switch to the user kde-devel: (the dash also changes to the new home directory)
 
<code bash>
 
<code bash>
su - kde-devel
+
su - kde-devel
 
</code>
 
</code>
  
Line 55: Line 55:
 
== Prepare for software setup ==
 
== Prepare for software setup ==
  
Please look also in [[Getting Started/Increased Productivity in KDE4 with Scripts]] .
+
Please look also in [[Getting Started/Increased Productivity in KDE4 with Scripts]].
  
Add these lines to your shell's configuration file, e.g. {{path|~/.bashrc}}.
+
You might first want to copy the {{path|~/.bashrc}} of your normal user account to the new kde-devel account.
<code bash>
 
export YACC='byacc -d'
 
export QTDIR=$HOME/qt-copy
 
export KDEDIR=$HOME/kde
 
export KDEDIRS=$KDEDIR
 
export DBUSDIR=$KDEDIR
 
export PKG_CONFIG_PATH=$DBUSDIR/lib/pkgconfig:$PKG_CONFIG_PATH
 
export PATH=$QTDIR/bin:$KDEDIR/bin:$PATH
 
export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH
 
export QT_PLUGIN_PATH=$KDEDIR/lib/kde4/plugins:$QT_PLUGIN_PATH
 
 
 
function cmakekde { cmake -DCMAKE_INSTALL_PREFIX=$KDEDIR \
 
-DCMAKE_BUILD_TYPE=debugfull $@ && make VERBOSE=1 && make install; }
 
## Uncomment if dbus doesn't work
 
#alias dbusstart="eval `PATH=$DBUSDIR/bin \
 
#$DBUSDIR/bin/dbus-launch --auto-syntax`"</code>
 
  
 +
Than copy and paste this [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|.bashrc]] to {{path|~/.bashrc}}.
  
 
Now either relogin or activate the settings with:
 
Now either relogin or activate the settings with:
 
<code bash>
 
<code bash>
source {{path|~/.bashrc}}
+
source ~/.bashrc
 
</code>
 
</code>
  
 
== Set up D-Bus ==
 
== Set up D-Bus ==
 
Skip this if you have D-Bus <nowiki>>=</nowiki>0.93 installed.
 
Skip this if you have D-Bus <nowiki>>=</nowiki>0.93 installed.
wget http://dbus.freedesktop.org/releases/dbus/dbus-1.0.2.tar.gz
+
<code bash>
tar xvfz dbus-1.0.2.tar.gz
+
wget http://dbus.freedesktop.org/releases/dbus/dbus-1.0.2.tar.gz
cd dbus-1.0.2/
+
tar xvfz dbus-1.0.2.tar.gz
./configure --disable-qt --disable-qt3 --prefix=$DBUSDIR \
+
cd dbus-1.0.2/
--localstatedir=/var && make && make install
+
./configure --disable-qt --disable-qt3 --prefix=$DBUSDIR \
dbus-uuidgen --ensure
+
--localstatedir=/var && make && make install
 
+
dbus-uuidgen --ensure
 +
</code>
 
== Set up CMake ==
 
== Set up CMake ==
  
Line 96: Line 82:
 
The default prefix is {{path|/usr/local}}, make sure {{path|/usr/local/bin}} is in your <tt>$PATH</tt>.
 
The default prefix is {{path|/usr/local}}, make sure {{path|/usr/local/bin}} is in your <tt>$PATH</tt>.
  
cd ..
+
<code bash>
wget http://www.cmake.org/files/v2.4/cmake-2.4.5.tar.gz
+
cd ..
tar zxf cmake-2.4.5.tar.gz
+
wget http://www.cmake.org/files/v2.4/cmake-2.4.5.tar.gz
mkdir cmake-build
+
tar zxf cmake-2.4.5.tar.gz
cd cmake-build
+
mkdir cmake-build
../cmake-2.4.5/bootstrap
+
cd cmake-build
make
+
../cmake-2.4.5/bootstrap
sudo make install
+
make
 
+
sudo make install
 +
</code>
 
== Set up Qt ==
 
== Set up Qt ==
cd ..
+
<code bash>
svn checkout svn://anonsvn.kde.org/home/kde/trunk/qt-copy
+
cd ..
cd ~/qt-copy && ./apply_patches && \
+
svn checkout svn://anonsvn.kde.org/home/kde/trunk/qt-copy
 +
cd ~/qt-copy && ./apply_patches && \
 
  ./configure -qt-gif -no-exceptions -debug -fast \
 
  ./configure -qt-gif -no-exceptions -debug -fast \
 
  -prefix $QTDIR -qdbus && make && make install
 
  -prefix $QTDIR -qdbus && make && make install
 
+
</code>
 
{{tip|If you get "error: X11/Xlib.h: No such file or directory", install the devel package of <tt>xorg</tt> (the actual name may vary between operating systems, for example xorg-devel on ubuntu).}}
 
{{tip|If you get "error: X11/Xlib.h: No such file or directory", install the devel package of <tt>xorg</tt> (the actual name may vary between operating systems, for example xorg-devel on ubuntu).}}
  
 
== Set up kdelibs ==
 
== Set up kdelibs ==
cd ..
+
 
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
+
If you use the aforementioned [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|.bashrc]] this is were those new functions come in handy:
mkdir kdelibs-build
+
 
cd kdelibs-build
+
<code bash>
cmakekde ../kdelibs
+
cs
 +
mkdir KDE && cd KDE
 +
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
 +
cd kdelibs
 +
cmakekde
 +
</code>
  
 
=== Additional KDE-specific CMake modules ===
 
=== Additional KDE-specific CMake modules ===
Line 135: Line 128:
 
Before ''kdebase'' you need to install ''kdepimlibs''
 
Before ''kdebase'' you need to install ''kdepimlibs''
  
cd
+
<code bash>
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
+
cs KDE
mkdir kdepimlibs-build
+
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
cd kdepimlibs-build
+
cd kdepimlibs
cmakekde ../kdepimlibs
+
cmakekde
 
+
</code>
 
== Set up kdebase ==
 
== Set up kdebase ==
 
You may need kdebase for some kioslaves.
 
You may need kdebase for some kioslaves.
cd
+
<code bash>
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase
+
cs KDE
mkdir kdebase-build
+
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase
cd kdebase-build
+
cd kdebase
cmakekde ../kdebase
+
cmakekde
 
+
</code>
 
=== Troubleshooting ===
 
=== Troubleshooting ===
 
If you have troubles compiling kdebase:
 
If you have troubles compiling kdebase:
Line 164: Line 157:
  
 
To build the API documentation for kdelibs, type the following:
 
To build the API documentation for kdelibs, type the following:
cd
+
<code bash>
mkdir apidox
+
cd
cd apidox
+
mkdir apidox
../kdelibs/doc/api/doxygen.sh ../kdelibs/
+
cd apidox
 
+
../kdelibs/doc/api/doxygen.sh ../kdelibs/
 +
</code>
 
== Success! ==
 
== Success! ==
  

Revision as of 13:53, 24 February 2007

Abstract

This tutorial shows one way to get KDE from trunk running. It consolidates info from several places, e.g. the official KDE developer pages. The official pages may be updated without this page being updated too, so check there if you have problems.

Note-box-icon.png
Note
Throughout the tutorial the bash shell is used. Expect a higher risk of build failure Monday when critical changes are implemented. Dashboard reports unexpected breakages. You are encouraged to fix failing modules.


Set up the development user account

Note-box-icon.png
Note
Instead of using the command line as described below, you can also use the User module in the KDE Control Center if you already have KDE3 installed.


useradd kde-devel mkdir /home/kde-devel passwd kde-devel chown kde-devel:kde-devel /home/kde-devel 2>/dev/null || \ chown kde-devel:users /home/kde-devel

Switch to the user kde-devel: (the dash also changes to the new home directory) su - kde-devel

The kde-devel User's Shell

On some systems a new user is configured by default to use /bin/sh. If this is not the case on your system, you can skip this section. Using /bin/sh can be very inconvenient to work with and you may want to change it to /bin/bash or another shell.

Note-box-icon.png
Note
To change the user's default shell you will need write access to /etc/passwd. Usually this means running a command as root. See below for a possible way to do this without requiring root privileges, but which will not work in all circumstances.


If your system comes with the usermod application you can run the following command as root: usermod -s /bin/bash.

If you don't have root privileges and your system supports the changing of your own shell with the chsh application, then you could try to change your shell to /bin/bash by using chsh -s /bin/bash your-kde-devel-username.

Another option is to use the vipw application as root to safely edit your /etc/passwd. Locate 'kde-devel' in the the file. Change '/bin/sh' at the end of the line to read '/bin/bash', save your changes and exit.

The new shell will be started automatically when you log in as the kde-devel user again.

Prepare for software setup

Please look also in Getting Started/Increased Productivity in KDE4 with Scripts.

You might first want to copy the ~/.bashrc of your normal user account to the new kde-devel account.

Than copy and paste this .bashrc to ~/.bashrc.

Now either relogin or activate the settings with: source ~/.bashrc

Set up D-Bus

Skip this if you have D-Bus >=0.93 installed. wget http://dbus.freedesktop.org/releases/dbus/dbus-1.0.2.tar.gz tar xvfz dbus-1.0.2.tar.gz cd dbus-1.0.2/ ./configure --disable-qt --disable-qt3 --prefix=$DBUSDIR \ --localstatedir=/var && make && make install dbus-uuidgen --ensure

Set up CMake

Skip this if you have CMake >=2.4.5 installed.

The default prefix is /usr/local, make sure /usr/local/bin is in your $PATH.

cd .. wget http://www.cmake.org/files/v2.4/cmake-2.4.5.tar.gz tar zxf cmake-2.4.5.tar.gz mkdir cmake-build cd cmake-build ../cmake-2.4.5/bootstrap make sudo make install

Set up Qt

cd .. svn checkout svn://anonsvn.kde.org/home/kde/trunk/qt-copy cd ~/qt-copy && ./apply_patches && \

./configure -qt-gif -no-exceptions -debug -fast \
-prefix $QTDIR -qdbus && make && make install

Ktip.png
 
Tip
If you get "error: X11/Xlib.h: No such file or directory", install the devel package of xorg (the actual name may vary between operating systems, for example xorg-devel on ubuntu).


Set up kdelibs

If you use the aforementioned .bashrc this is were those new functions come in handy:

cs mkdir KDE && cd KDE svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs cd kdelibs cmakekde

Additional KDE-specific CMake modules

There are additional CMake modules in kdelibs/cmake/modules/ that are necessary for building KDE4 applications. These will be installed for you when kdelibs itself is installed.

Troubleshooting

If you have problems compiling kdelibs, first make sure the following commands can be executed: gcc, g++, pkg-config.

Ktip.png
 
Tip
If you get "Could NOT find GIF", install the devel package of libungif (the actual name may vary between operating systems).
Ktip.png
 
Tip
In order to avoid compilation problems, GCC should be at least of version 4.1. The minimum supported compiler is not yet determined at the time of writing this.


If the problems persist, try the make-option --keep-going

Set up kdepimlibs

Before kdebase you need to install kdepimlibs

cs KDE svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs cd kdepimlibs cmakekde

Set up kdebase

You may need kdebase for some kioslaves. cs KDE svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase cd kdebase cmakekde

Troubleshooting

If you have troubles compiling kdebase:

  • Make sure you have the libxss headers installed. (Usually you got undefined references on xscreensaver objects if you haven't those headers)
  • which meinproc has to deliver /home/kde-devel/kde/bin/meinproc
  • if cmakekde cannot find the path of kdepimlibs, edit the file /home/kde-devel/kdebase-build/CMakeCache.txt and manually set KDEPIMLIBS_INCLUDE_DIR:PATH=/home/kde-devel/kdepimlibs-build
  • if you get an error saying "Please set the following variables: X11_XTest_LIB (ADVANCED)", install the devel package of Xtst. On some systems, this is packaged separately from xext and called x11proto-xext-dev or libxtst-dev. You may also need to remove the CMakeCache.txt file in the build dir after installing the package.
  • the same for "X11_Xinerama_LIB (ADVANCED)" where you will need the devel package for xinerama.

Generating local API documentation

Although the API documentation for KDE is available online at api.kde.org, it is sometimes useful to have it on your own disk, for example when you want to use KDevelop for browsing the documentation or when you are not able to be online all the time.

Be aware that generating the API documentation can take several hours and takes almost half a gigabyte of diskspace. The generation is handled by a script in kdelibs/doc/api, you need doxygen to be able to run it.

To build the API documentation for kdelibs, type the following: cd mkdir apidox cd apidox ../kdelibs/doc/api/doxygen.sh ../kdelibs/

Success!

You are now ready to start building other svn modules in the same fashion as you built kdebase, running and testing KDE4 or writing your own patches and applications.

See the Starting a KDE4 Environment and Applications tutorial for how to start working on your new KDE4 installation.

Additional notes


Content is available under Creative Commons License SA 4.0 unless otherwise noted.