< Getting Started | BuildRevision as of 17:42, 26 February 2007 by 220.127.116.11 (talk | contribs) (→Set up kdelibs: Added missing step for creating ~/src/ and ~/build/)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Building KDE4 From Source Tutorial Series Getting Started Previous Anonymous SVN Quickstart Guide What's Next Starting a KDE4 Environment and Applications Further Reading kdesvn-build: The KDE From Subversion Build ToolIncreased Productivity in KDE4 with ScriptsIntroduction to CMakeInstructions for Mac OS X Contents 1 Abstract 2 Required Software 3 Create a user account for KDE4 development 3.1 Option 1: Command Line 3.2 Option 2: Using KControl 3.3 Setting up the environment 3.4 Switching to the New User 4 The development user's shell 4.1 Option 1: As the kde-devel user 4.2 Option 2: As the root user 5 Set up D-Bus 5.1 The Recipe 5.2 What's Happening 6 Set up CMake 6.1 The Recipe 6.2 What's Happening 7 Set up Qt 7.1 The Recipe 7.2 What's Happening 8 Set up kdelibs 8.1 The Recipe 8.2 What's Happening 8.3 Additional KDE-specific CMake modules 8.4 Troubleshooting 9 Set up kdepimlibs 9.1 The Recipe 9.2 What's Happening 10 Set up kdebase 10.1 Troubleshooting 11 Generating local API documentation 12 Success! Abstract This tutorial shows one way to get KDE from trunk running on Linux/BSD systems. Throughout the tutorial the bash shell is used. If you are interested in building KDE on other systems such as Solaris, MacOS or Microsoft Windows, please visit the Build page and see the links at the bottom for the respective operating systems. Note Expect a higher risk of build failure Monday when critical changes are implemented. Dashboard reports unexpected breakages. You are encouraged to fix failing modules. Required Software The following must be installed first before you can successfully complete this tutorial: gcc and g++ from the gcc project, preferably version 4.1 or higher svn, the subversion revision control client pkg-config development libraries and headers for X11 development library and headers for libungif You may also want to have the following installed: bash Create a user account for KDE4 development Option 1: Command Line 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 Option 2: Using KControl Instead of using the commands above, you can also use the User module in the KDE Control Center if you already have KDE3 installed. Setting up the environment Copy the ~/.bashrc from your normal user account to the new kde-devel account. Next, copy and paste the contents of .bashrc into ~kde-devel/.bashrc. This will provide access to commands such as cmakekde that are used in this tutorial as well as ensure that the proper paths are in place for Qt, KDE and CMake binaries. For more information, please read the Getting Started/Increased Productivity in KDE4 with Scripts tutorial. Switching to the New User Switch to the user kde-devel: (the dash also changes to the new home directory) su - kde-devel The rest of this tutorial assumes you are running as the kde-devel user. The development 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. Option 1: As the kde-devel user 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. Option 2: As the root user If your system comes with the usermod application you can run the following command as root: usermod -s /bin/bash. s 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. Set up D-Bus Skip this if you have D-Bus >=0.93 installed. The Recipe 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 What's Happening D-Bus source code is downloaded from freedesktop.org (line 1) and unpacked (line 2). After going into the newly created D-Bus directory (line 3), the build is set up using the supplied configure script (lines 4-5). Finally, using dbus-uuidgen D-Bus is set to start automatically when the desktop session starts (line 6). Set up CMake Skip this if you have CMake >=2.4.5 installed. The Recipe 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 What's Happening First, we go back to the kde-devel user's home directory (line 1), get the CMake sources (line 2) and unpack them (line 3). We create a directory to build CMake in (line 4) and go into it (line 5). We then run the CMake boostrap script to set up the CMake build (line 6), then make (line 7) and install it (line 8) using the root user. If your system does not have the sudo command, you can instead do su -c "make install". Set up Qt Next we need to get the Qt4 that is in KDE's source repository. This version of Qt is the one that KDE4 is guaranteed to build against as well as having some extra patches that will be in future bug fix releases of Qt from Trolltech. The Recipe 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 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). What's Happening We switch back to the kde-devel user's home (line 1) and download the source code using subversion (sv) from KDE's repository (line 2). After changing into the resulting ~/qt-copy directory (line 3), we run a script that manages the patches that come with qt-copy (line 4). Once the patches have been applied, we then set up the build using the configure script (line 5-6). The various command line options used are explained in the ~/qt-copy/README.qt-copy file. Finally, we build (line 7) and install (line 8) Qt. Note that the installation does not require root as it installs it locally into ~/qt-copy. Set up kdelibs With Qt4 built, we can now move on to building KDE's base libraries. If you use the aforementioned .bashrc this is where those new functions come in handy. Please note that for the functions cs and cb to work, you will need to create the directories ~/src and ~/build with the command 'mkdir ~/src ~/build'. The Recipe cs mkdir KDE && cd KDE svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs cd kdelibs cmakekde What's Happening We change to the base source directory (line 1) then make and go into the KDE directory (line 2). We download the sources for kdelibs using subversion (line 3), go into the new ~/KDE/kdelibs directory (line 4), and commence the build (line 6). This will leave us in the kdelibs build directory after the build is completed. 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 software in the "Required Software" section above is installed and works. Other possible hints include: If you received an error stating "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there." then you need to change to your build directory before running cmakekde. (e.g cs kdelibs && cb && cmakekde) If the problems persist, try the CMake make-option --keep-going. Here you need the libungif library, otherwise you will get an error. Set up kdepimlibs After kdelibs, but before kdebase, you need to build and install kdepimlibs. The Recipe cs KDE svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs cd kdepimlibs cmakekde What's Happening We go into the KDE source directory (line 1), download the source code for kdepimlibs using subversion (line 2) and then go into the new ~/KDE/kdepimlibs directory (line 3). We then commence the build (line 4). This will leave us in the kdepimlibs build directory after the build is completed. 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. Retrieved from "https://techbase.kde.org/index.php?title=Getting_Started/Build/KDE4&oldid=8396" Categories: TutorialBuild KDEKDE4 Content is available under Creative Commons License SA 4.0 unless otherwise noted.