KDE TechBase - User contributions [en]

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KOrganizer

2008-08-14T11:47:11Z

Doviende:

===KOrganizer===

====Application specific tips====
any application specific tips go here.

I just recently rewrote the todo view completely. The rewrite is done, would be great if you could give it a throughout test. (nick:chiefaua, svn:thrainer)

====Testers====
Please put your IRC nickname and KDE PIM svn revision number in the table if you are testing this app.
{|
|-
!IRC Nickname !! KDE PIM svn revision number tested. || Testing details
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r803492 || not tested yet ||
|-
|[[User:finex|FiNeX]]||svn r811489 || testing ||
|-
|[[User:Talavis|talavis]] || svn r818299 || testing ||
|-
|[[User:Doviende|doviende]] || svn r846116 || testing ||
|}

====Bugs====
Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with <nowiki>~~~</nowiki>.

*<s>[[User:finex|FiNeX]] On the calendar views (month/day/week) after selecting a range, if you start type a new event is created. You can do this only one time, after you have to close/restart korganizer for repeat this behaviour.</s>
**<s>[[User:finex|FiNeX]] Moreover on 3.5 what you typed were used as event title, this doesn't happen anymore.</s>
**[[User:vkrause|Volker]] Fixed in revision 813635.

*<s>[[User:finex|FiNeX]] crash on "file"->"Export"->"upload new hot stuff". No backtrace, this is the shell output: http://pastebin.ca/1028758</s>
**<s> [[User:Krop|Krop]] Backtrace : http://pastebin.com/m7171fc13 </s>
** Filed as {{Bug|165076}} [[User:Grundleborg|Grundleborg]]

*<s> [[User:finex|FiNeX]] start/end date on "event" dialog is too small: the first two digits of the year are cutted out. http://img338.imageshack.us/img338/6388/korganizerdateshq1.jpg</s>

*<s>[[User:finex|FiNeX]] "Edit reminders" dialog: the offset column text is between "<html>...</html>".</s>
*<s>[[User:finex|FiNeX]] "Edit event" file dialog: "Calendar:..." label too near to "Categories" label. It is confusing.</s>

*<s> [[User:finex|FiNeX]] "Manage templates" dialog: if you have zero templates and you click on "apply template" the "new" button is disabled.</s>
**<s> [[User:finex|FiNeX]] Patch for disabling the "apply template" button when there are zero templates: http://pastebin.ca/1028787 committed (authorized by winterz)</s>

*<s> [[User:finex|FiNeX]] Tooltips on events display "&nbsp;"</s>

* <s> Menu item "help > about korganizer" change icon when hovering.</s> -- gemegik, [[User:Med|Med]]

*<s> A lot of menu items (most?) are missing when Korganizer is run stand-alone, but they are there when using kontact to browse the korganizer parts.</s> [[User:Talavis|talavis]]

* Opening korganizer stand-alone will open only the part last selected in Kontact, and it's impossible to show any toolbars or anything (related to the above bug?) [[User:Talavis|talavis]]

* create new event, change start time to "7am", hit "ok". i get a window saying "please specify a valid start time, for example '04:18 am', and then the whole event window closes, dropping all my information. This should just let me continue to edit the event, unless i decide to press "cancel" instead of "ok". Also, "7am" and "7pm" should be recognized as times, IMHO. [[User:Doviende|Doviende]]

* create new event, enable "time associated", set the start and end time, then make it a new template by going to "manage templates" and pressing "new". Then go make another event and apply this template...it will enable "time associated" for you, but it won't set the times. [[User:Doviende|Doviende]]

* in events, "19:00" is not recognized as a time, forced to use only "07:00 pm" [[User:Doviende|Doviende]]

* severe bug in dates: create a new event, enable "time associated", click on the "end" date field and press the up-arrow. notice that the "08" for the year will now say just "8", and it actually means the year "8" instead of "2008". if you hit "apply" now, it'll say that your end time is before your start time. You can not fix the field back to 2008 without cancelling the event entirely and starting over again. [[User:Doviende|Doviende]]
** do the previous action, then click on "start date" field and press up-arrow. start date will now be 2000 years back too, but look at the end date now. it will have an additional 2000 years subtracted, and it will say "-1993" for the year. [[User:Doviende|Doviende]]

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KOrganizer

2008-08-14T11:33:43Z

Doviende:

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KOrganizer

2008-08-14T11:32:11Z

Doviende:

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KOrganizer

2008-08-14T11:11:03Z

Doviende:

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KOrganizer

2008-08-14T11:10:32Z

Doviende:

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KOrganizer

2008-08-14T11:06:38Z

Doviende:

User:Doviende

2008-08-14T11:05:12Z

Doviende:

Hey, i'm sorta new to kde. trying to help out with bugsquad. you can find me on #kde-bugs and #kde-cafe

User:Doviende

2008-08-14T11:04:49Z

Doviende: New page: Hey, i'm sorta a newb. trying to help out with bugsquad. you can find me on #kde-bugs and #kde-cafe

Hey, i'm sorta a newb. trying to help out with bugsquad. you can find me on #kde-bugs and #kde-cafe

Getting Started/Build/Distributions/Debian

2008-08-13T05:47:50Z

Doviende: added librdf-dev to optional list

{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4/Kubuntu and Debian}}
This page details installation of kde4 requirements on Kubuntu 7.10 (Gutsy) and Debian (Testing/Unstable). For a basic functioning desktop, the recommended packages are installed with the command:

<code bash>
sudo aptitude install build-essential cdbs debhelper cmake \
kdesdk-scripts subversion ssh xserver-xephyr doxygen dbus-x11 \
libstreamanalyzer-dev libstrigiqtdbusclient-dev \
libxml2-dev libxslt1-dev shared-mime-info libgif-dev libssl-dev \
libboost-dev libgpgme11-dev libxine-dev libqimageblitz-dev libbz2-dev \
libdbus-1-dev libpam0g-dev libpcre3-dev libkrb5-dev libsm-dev \
libclucene0ldbl libclucene-dev libjpeg62-dev libxtst-dev xsltproc
</code>

This installs build prerequisites such as build essential, almost all compilation requirements for kde4 (with the exception of qt4) and some recommended packages such as libssl-dev for https support. Further recommended and optional packages are listed below.

To install all the optional packages:

<code bash>
sudo aptitude install build-essential cdbs debhelper cmake \
kdesdk-scripts subversion ssh xserver-xephyr doxygen graphviz libqt4-dev \
dbus-x11 libstreamanalyzer-dev libstrigiqtdbusclient-dev libxml2-dev \
libxslt1-dev shared-mime-info libgif-dev libpcre3-dev libssl-dev libbz2-dev \
libpcre3-dev libxml2-utils libpcre3-dev libopenexr-dev libjasper-dev \
libenchant-dev libavahi-common-dev libaspell-dev libasound2-dev libboost-dev \
libgpgme11-dev libldap2-dev libsasl2-dev libxine-dev libqimageblitz-dev \
libsmbclient-dev libxkbfile-dev libxcb1-dev libxklavier12-dev libxdamage-dev \
libxcomposite-dev libbluetooth-dev libusb-dev libcaptury-dev \
network-manager-dev libsmbclient-dev libsensors-dev \
libpam0g-dev libnm-util-dev libusb-dev libcfitsio3-dev libnova-dev \
libeigen-dev libopenbabel-dev libfacile-ocaml-dev libboost-python-dev \
libqca2-dev libqca2-dev libqca2-dev libsvn-dev libsvncpp-dev \
libcommoncpp2-dev libidn11 libidn11-dev libxtst-dev librdf-dev
</code>

To compile the stable release of kde4 (kde4.0) also install the package <tt>libqt4-dev</tt>.

To compile kde from trunk (soon to be kde4.1) the latest Qt4.4 snapshot must be compiled from source. This is provided conveniently in the kde svn repository as qt-copy. Please read README.qt-copy for the necessary Qt options as well as currently known problems.

It may be installed with the following commands:

<code bash>
cs # Note: cs is not a typo.
svn checkout svn://anonsvn.kde.org/home/kde/trunk/qt-copy
cd qt-copy
./apply_patches
cb # Build Qt in a separate build directory
../../src/qt-copy/configure <Qt options here> --prefix $QTDIR
make -j2 # use 'make -j(X+1)' where X is your number of processors, to compile faster
# if we don't install, we'll just clear obj files to
# save disk space
if [ "$QTDIR" = "`pwd`" ]; then \
find . -name '*.o' -delete ; \
else make install; fi;

</code>

After installing required and desired packages, proceed to [[Getting_Started/Build/KDE4#kdelibs|building KDE 4]].

== Build prerequisites ==
In Kubuntu 7.10 (Gutsy) and Debian (Testing/Unstable) the build prerequisites are installed with:

<code bash>
sudo aptitude install build-essential cdbs debhelper cmake \
kdesdk-scripts subversion ssh xserver-xephyr
</code>

Optional packages for API documentation generation:
<code bash>
sudo aptitude install doxygen graphviz
</code>

== kdelibs dependencies ==

Kdelibs dependencies can be installed with:
<code bash>
sudo aptitude install libqt4-dev dbus-x11 \
libstreamanalyzer-dev libstrigiqtdbusclient-dev \
libxml2-dev libxslt1-dev shared-mime-info libgif-dev libpcre3-dev \
libjpeg62-dev
</code>

=== Recommended packages ===
* libssl-dev - Needed for https support etc.
* libbz2-dev - Needed for bzip support in kio_archive and GHNS packages.
* libpcre3-dev - regular expression library. Recommended for Javascript support.

<code bash>
sudo aptitude install libssl-dev libbz2-dev libpcre3-dev
</code>

=== Optional packages ===
* libasound2-dev - The Alsa sound system
* libaspell-dev - spell checking support (in kwrite etc)
* libavahi-common-dev - avahi/zeroconf service discovery
* libenchant-dev - spell checking wrapper library
* libjasper-dev - image processing library
* libopenexr-dev - image processing library
* libxml2-utils - used to validate generate doc files
<code bash>
sudo aptitude install libasound2-dev libaspell-dev \
libavahi-common-dev libenchant-dev libjasper-dev libopenexr-dev \
libxml2-utils
</code>

== kdepimlibs dependencies ==
kdepimlibs dependencies can be installed with:
<code bash>
sudo aptitude install libboost-dev libgpgme11-dev
</code>

=== kdepimlibs recommended ===
* libldap2-dev - For ldap support in kde4.
* libsasl2-dev - Required for imap and sieve kioslaves
<code bash>
sudo aptitude install libldap2-dev libsasl2-dev
</code>

== kdebase dependencies ==
kdebase-runtime dependencies can be installed with:
<code bash>
sudo aptitude install libxine-dev
</code>

{{Note|Note that libxine1-dev depends on gnome packages due to a kubuntu gutsy packaging bug (fixed in hardy). Also kubuntu packages xinelib version 1.1.8, which has trouble playing short sounds (fixed in xinelib 1.1.9).
}}

kdebase-apps dependencies can be installed with:
<code bash>
sudo aptitude install libqimageblitz-dev
</code>

=== kdebase-apps optional ===
* libxcb1-dev - X C binding - Used for video widget support in xine
* libxkbfile-dev - keyboard configuration package
* libsmbclient-dev - for samba support in kde4

<code bash>
sudo aptitude install libsmbclient-dev libxkbfile-dev libxcb1-dev
</code>

=== kdebase-workspace optional ===
* libsmbclient-dev - for samba support in kde4
* network-manager-dev - Can be used by solid for network management
* libcaptury-dev - video capturing tool for screencasts
* libusb-dev - for usb support in solid
* libbluetooth-dev - for bluetooth support in solid
* libxcomposite-dev - for compositing support in kwin
* libxdamage-dev - for compositing support in kwin
* libxklavier11-dev - virtual keyboard
* libsensors-dev - Support for hardware sensors (eg, temperature, fans)
* libpam0g-dev - Authentication module
* libnm-util-dev - needed to build solid with network manager
<code bash>
sudo aptitude install libxklavier11-dev libxdamage-dev libxcomposite-dev \
libbluetooth-dev libusb-dev libcaptury-dev network-manager-dev \
libsmbclient-dev libsensors-dev libpam0g-dev libnm-util-dev
</code>

== kdeedu ==
The following packages are recommended if you intend to use kstars:

* libfacile-ocaml-dev - used by kalzuim.
* libboost-python-dev - optional for kig.
* libreadline-dev - Gives kalgebra a console interface.
* libopenbabel-dev - used by kalzium.
* libeigen-dev - used by kalzium.
* libusb-dev - Provides KStars INDI support.
* libcfitsio3-dev - Gives KStars support for FITS images.
* libnova-dev - A general purpose, double precision, Celestial Mechanics, Astrometry and Astrodynamics library for KStars.

<code bash>
sudo aptitude install libusb-dev libcfitsio3-dev libnova-dev libeigen-dev \
libopenbabel-dev libfacile-ocaml-dev libboost-python-dev
</code>

== koffice ==
* libqca2-dev - qt cryptographic support.

== kdepim ==
* libqca2-dev - qt cryptographic support.

== kdenetwork ==
* libqca2-dev - qt cryptographic support. Used for jabber protocol.

== kdevplatform ==
* libsvn-dev - subversion support for the dev platform.
* libsvncpp-dev - subversion support for the dev platform.
* libcommoncpp2-dev - teamwork integration.

== kdevelop ==
Requires kdevplatform.

Return to [[Getting_Started/Build/KDE4#kdelibs|building KDE 4]].

Getting Started/Build/KDE4

2008-08-13T05:45:29Z

Doviende: added clarification about what's in kdesupport.

{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4}}

{{TutorialBrowser|

series=Getting Started|

name=Building KDE4 From Source|

pre=[[../../Sources/Anonymous_SVN|Anonymous SVN Quickstart Guide]]|

next=[[../../Set_up_KDE_4_for_development|Set up KDE 4 for development]]|

reading=[[../kdesvn-build|kdesvn-build: The KDE From Subversion Build Tool]] [[../../Increased_Productivity_in_KDE4_with_Scripts|Increased Productivity in KDE4 with Scripts]] [[Development/Tutorials/CMake |Introduction to CMake]] [[../KDE4/FreeBSD|FreeBSD notes]] [[../KDE4/Mac OS X|Instructions for Mac OS X]] [[../KDE4/Windows|Instructions for MS Windows]]|
}}

== Abstract ==

This tutorial shows one way to get KDE from trunk running on Linux/BSD systems. There are also tutorials for [[Getting_Started/Build/KDE4/FreeBSD|FreeBSD]], [http://www.kdelibs.com/ Windows], [[Getting_Started/Build/KDE4/Mac OS X|Mac OS X]] and [http://solaris.kde.org/ Solaris]. Throughout the tutorial the bash shell is used.

{{warning|Expect a higher risk of build failure '''on Mondays''' when most kdelibs changes are committed. [http://developer.kde.org/~dirk/dashboard/ Dashboard] reports unexpected breakages. You are encouraged to fix failing modules.}}

== Create a user account for KDE4 development ==

{{Note|
Some people like to have a separate user account for KDE 4 (for instance an old bug deleted files by mistake), and the instructions below were written with that approach.

However it is much more efficient to do everything with a single user account, see [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|Increased Productivity in KDE4 with Scripts]]
for more details.

You can still follow the instructions below, but don't put the environment variables in your <tt>.bashrc</tt>, put them in a separate file that you source to switch to the KDE 4 environment.
}}

=== Option 1: Command Line ===
{{Note|
On some systems a new user is configured by default to use {{path|/bin/sh}}. Using {{path|/bin/sh}} can be very inconvenient to work with and you may want to change it to {{path|/bin/bash}} or another shell.
On Ark Linux and Fedora, you can skip the <tt>-s /bin/bash</tt> switch - {{path|/bin/sh}} is {{path|bash}}.
}}
<code bash>
useradd -m kde-devel -s /bin/bash
passwd kde-devel
</code>

{{Warning|
The new kde-devel user will not be added automatically to all the user groups, which will result in not having sound, not being able to sudo, etc. Edit your /etc/groups file to add the kde-devel user to all the groups that you need (probably the groups that your usual username is already assigned to).
}}

=== 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 {{path|~/.bashrc}} from your normal user account to the new kde-devel account. Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4#Required Software|makeobj]]</tt> command available. Alternatively, you can download the kde-sdk package (or perform a subversion checkout) and include the kde-sdk/scripts/ directory in your path. You will probably also want to modify the path to make sure it doesn't include your kde3 paths. Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]).
To make it run, you have to open a new bash or to execute
<code bash>
source ~/.bashrc
</code>

This will provide access to commands such as <tt>cmakekde</tt> 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: (don't forget the dash)
<code bash>
ssh -X kde-devel@localhost
</code>

{{Note|
If the ssh command fails, check out the [[Getting_Started/Set_up_KDE_4_for_development#Launching_KDE_4_apps|Launching KDE 4 apps]] section of the [[Getting_Started/Set_up_KDE_4_for_development|KDE4 development guide]].
}}

== Required packages from your distribution ==
The requirements to build kde4 from source vary from distribution to distribution. Instructions for your distribution are provided below:

* [[Getting_Started/Build/KDE4/Ark Linux|Ark Linux]]
* [[Getting_Started/Build/KDE4/Arch Linux|Arch Linux]]
* [[Getting_Started/Build/KDE4/Fedora|Fedora]]
* [[Getting_Started/Build/KDE4/Kubuntu and Debian|Kubuntu and Debian]]
* [[Getting_Started/Build/KDE4/openSUSE|openSUSE]] Note: there is a [http://en.opensuse.org/KDE/Developing/Guide specific guide for openSUSE].
* [[Getting_Started/Build/KDE4/Gentoo|Gentoo]]
* [[Getting_Started/Build/KDE4/LFS|Linux from Scratch]] or to build from source.
* [[Getting_Started/Build/KDE4/Mandriva|Mandriva]]

* [[Getting_Started/Build/KDE4/Generic|any other distro]]

Your next compilation step depends on the packages supplied by your distro.

=== Compiling qt-copy, HAL etc. ===
If you do not want to use the packages provided by your distro you can compile things like Qt yourself. Instructions for building all dependencies including HAL, Cmake, Qt4 (qt-copy) and kde-support are available in [[Getting_Started/Build/KDE4/Prerequisites|the build prerequisites page]]. Note that automoc, phonon, strigi, soprano, and a few other things are part of kdesupport, so if you have errors about these missing, you'll need to get kdesupport.

== Building KDE for development or stable use ==

The commands below are used to build the latest unstable version of KDE from trunk. This should not be used in a production environment, but is recommended for developers.

To build the stable version of KDE4, change the svn checkout commands below to <tt>branches/KDE/4.0/</tt> instead of <tt>trunk/KDE/</tt>, ie:

svn checkout svn://anonsvn.kde.org/home/kde/branches/KDE/4.0/kdelibs

svn checkout svn://anonsvn.kde.org/home/kde/branches/KDE/4.0/kdepimlibs

svn checkout svn://anonsvn.kde.org/home/kde/branches/KDE/4.0/kdebase

etc...

== kdelibs ==

We can now move on to building KDE's base libraries.

=== The Recipe ===
cd
cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]
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 {{path|~/kde/src/KDE/kdelibs}} directory (line 4), and commence the build (line 5). This will leave us in the <tt>kdelibs</tt> build directory after the build is completed.

{{tip|There might be missing dependencies on your system! They are easily overlooked in the output of <tt>cmakekde</tt>.
You might want to do a <tt>cmake $KDE_SRC/KDE/MODULE_NAME</tt> prior to compiling any kde modules (like kdelibs, kdepimlibs etc.)}}

=== Additional KDE-specific CMake know-how ===

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

To make a non-debug-release (e.g. suppressing all kDebug() messages), use e.g.
cmake -DCMAKE_BUILD_TYPE=Release . && make && make install

=== Troubleshooting ===

For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdelibs|kdelibs troubleshooting section]].

== kdebase ==
kdebase is divided into three parts:
* '''apps'''
:This contains applications like Dolphin or KWrite.
* '''runtime'''
:This contains things needed by every application at runtime, like icons. It is a required dependency for each KDE application, so you have to compile and install this.
* '''workspace'''
:This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.

You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <code bash>cd kdebase</code> with <code bash>cd kdebase/runtime</code> in the recipe below.

=== The Recipe ===
cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase
cd kdebase
cmakekde

=== Troubleshooting ===
For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdebase|kdebase troubleshooting section]].

== Running KDE 4 programs ==

You can now run KDE 4 programs (e.g. kwrite) by typing:
ssh -X kde-devel@localhost
kwrite

=== Troubleshooting ===

For troubleshooting issues see [[Getting_Started/Build/KDE4/Troubleshooting#Running_programs|troubleshooting running programs]].

== kdepimlibs ==
It is a good idea to build kdepimlibs, since some other packages require it (within KDE those are kdepim, kdeutils and kdenetwork).

=== The Recipe ===
cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]
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 {{path|~/kde/src/KDE/kdepimlibs}} directory (line 3). We then commence the build (line 4). This will leave us in the <tt>kdepimlibs</tt> build directory after the build is completed.

=== Troubleshooting ===

For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdepimlibs|kdepimlibs troubleshooting section]].

== Generating local API documentation ==

See the [[Development/Tools/apidox|generating apidox]] page.

== Staying up to date ==

In order to keep the kde4 installation up to date, each of the modules installed should be updated periodically. As Monday is the day for big changes in kdelibs, Tuesday may be the best day to do this. For each module checked out, run <tt>svn up</tt> and <tt>make</tt>.

For example:
<code bash>
cs kdesupport # cs is not a typo
svn up
cb # cb is not a typo
make install
</code>

Note: it is not necessary to run cmakekde for updates.

== Installing a subset of a module ==

Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:

<code>
add_subdirectory(libkdegames)
add_subdirectory(libkmahjongg)

macro_optional_add_subdirectory(doc)
macro_optional_add_subdirectory(lskat)
macro_optional_add_subdirectory(katomic)
</code>

So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:

<code bash>
cs KDE
svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames # The -N switch performs a non-recursive checkout
cd kdegames
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/libkdegames # Get required directories
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/libkmahjongg
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/cmake
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/kbattleship # Get optional directories
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/kmahjongg
cmakekde
</code>

== 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 [[Getting Started/Set up KDE 4 for development|Set up KDE 4 for development]] tutorial for how to start KDE 4 applications and how to use KDevelop to work on them.

[[Category:Build KDE]]
[[Category:KDE4]]

Getting Started/Build/Troubleshooting

2008-08-13T05:30:09Z

Doviende: added more clear mention of kdesupport

{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4/Troubleshooting}}

{{TutorialBrowser|

series=Getting Started|

name=Building KDE4 From Source/Troubleshooting|

pre=[[../|KDE SVN Quickstart Guide]]|

next=[[../|KDE SVN Quickstart Guide]]|
|
}}

This page contains some troubleshooting tips for issues you may encounter while building kde4 from source.

Many of the issues listed here may be out of date.

== Issues building kdelibs ==
If you have problems compiling kdelibs, first make sure the software in the [[Getting_Started/Build/KDE4#Software_Requirements|Required Software]] section above is installed and works. If you install additional software, it may be necessary to remove {{path|~/kde/src/KDE/kdelibs/CMakeCache.txt}} before trying the build again. In particular, pay attention to the requirement of kdesupport (such as the components for automoc, strigi, phonon, etc).

Other possible hints include:
* If the <tt>cmakekde</tt> command fails stating that CMake requires an out of source build directory, remove {{path|~/kde/src/KDE/kdelibs/CMakeCache.txt}}, and try again.

If <tt>cmakekde</tt> still gives the same error then try this
cd
cmake -DCMAKE_INSTALL_PREFIX=$KDEDIR \
-DCMAKE_BUILD_TYPE=debugfull \
-DKDE4_BUILD_TESTS=ON \
~/kde/src/KDE/kdelibs
make
make install
* 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 <tt>cs KDE/kdelibs && cb && cmakekde</tt>) If the message stays, run 'svn status' in the kdelibs directory and remove all files labeled with '?'.
* If Qt wasn't found or the wrong version of Qt was found, make sure that the qmake from the Qt you need is the first qmake in the path.
* If qmake wasn't found and you are using Debian packages, /usr/bin/qmake probably points to a wrong qmake version. To fix this run as root:
update-alternatives --config qmake
* If the problems persist, try the CMake make-option <tt>--keep-going</tt>.
* Here you need the libungif library, otherwise you will get an error message like "<tt>Could NOT find GIF</tt>".
* Qt-4.3 upgrade: if you get a link error in kjsembed talking about QScriptEngine, edit CMakeCache.txt in kdelibs and remove the lines that talk about QT_QTUITOOLS_LIBRARY, then type make again (that static library has a new dependency, and the cmake code that adds it needs to run).
* if you get <code>CMake Error: KDE Requires Qt to be built with SSL support
</code>, install openssl-devel, remove CMakeCache.txt and re-compile QT.
* if you get <code>kdelibs/kimgio/ico.cpp:188: undefined reference to `QImage::jumpTable()'</code> it means you compiled QT without QT3 support(no, linking to a true QT3 install won't work)
* if none of the errors above match yours, you might just try a quick'n'dirty <code>make clean</code> in kdelibs.
* if you get "The PCRE regular expression library has not been found >=4.5 " then watch out the http://techbase.kde.org/index.php?title=Getting_Started/Build/KDE4/Kubuntu_and_Debian (Getting Started/Build/KDE4/Kubuntu and Debian-> kdelibs dependancies ->Recommended packages ) or
remove ../.. build/kdelibs
cs KDE/kdelibs
cmakekde

* [stub] What to do if you have a problem like kde-config.cpp:56: undefined reference to `KLocalizedString::~KLocalizedString()' and
/Depot/Temp/kdelibs-4.0.2/kdecore/kde-config.cpp:197: undefined reference to `KConfigGroup::readPathEntry(char const*, QString const&) const' and kde-config.cpp:66: undefined reference to `ki18n(char const*)'?
Seems to happen with some localization stuff

== Issues building kdebase ==
If you have troubles compiling kdebase:
* XINE is needed to compile kdebase-runtime
* Make sure you have the <tt>libxss headers</tt> installed. (Usually you got undefined references on xscreensaver objects if you do not have those headers)
* <tt>which meinproc4</tt> has to deliver {{path|/home/kde-devel/kde/bin/meinproc4}}
* if cmakekde can not find the path of kdepimlibs, edit the file {{path|$KDE_BUILD/KDE/kdebase/CMakeCache.txt}} and manually set <tt>KDEPIMLIBS_INCLUDE_DIR:PATH=$KDE_BUILD/kdepimlibs</tt>
* if you get an error saying "Please set the following variables: X11_XTest_LIB (ADVANCED)", install the devel package of <tt>Xtst</tt>. On some systems, this is packaged separately from <tt>xext</tt> and called <tt>x11proto-xext-dev</tt> or <tt>libxtst-dev</tt>. 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 <tt>xinerama</tt>.
* if you get an error complaining about a missing variable X11_Xrandr_LIB, you need the devel package for libxrandr (libxrandr-devel on ubuntu-systems)
* if you get the error "Please set the following variables: FONTCONFIG_INCLUDE_DIR, FONTCONFIG_LIBRARIES (ADVANCED)", then you need to install the libfontconfig headers
* if you get the error "CMake Error: This project requires some variables to be set, and cmake can not find them. Please set the following variables: KMETADATA_LIBRARIES", you need to install soprano from kdesupport and to rebuild kdelibs
* if you get the error "‘XserverRegion’ does not name a type" make sure you have libxcomposite headers installed (<tt>libxcomposite-dev</tt> in ubuntu)
* if you get the error "CMake Error: This project requires some variables to be set, and cmake can not find them. Please set the following variables: QT_QTOPENGL_LIBRARY (ADVANCED) ", try editing CMakeCache.txt and setting QT_QTOPENGL_LIBRARY:FILEPATH=/home/kde-devel/qt-copy/lib/libQtOpenGL.so

* if you get messages as "KDE4_INSTALL_HANDBOOK() is deprecated. Remove it please. Now all is done in KDE4_CREATE_HANDBOOK." then, either find the files containing the offending line and comment it out manually, or run the following script in ~/kde/src/KDE/kdebase: [http://www.plamadeala.com/files/macros_corrector.sh macros_corrector.sh]. It will just REMOVE the line that has "kde4_create_handbook" in it from all the found files.
*If you get an error (in ubuntu) concerning libxtst.so install the libxtst-dev package
* If you get the message "kdebase/workspace/kcontrol/kxkb/x11helper.cpp:131: error: ‘KGlobal’ has not been declared", you might need to install libxklavier development packages.
* If you get "/home/kde-devel/kde/lib/libkio.so: undefined reference to `Strigi::AnalysisResult::AnalysisResult(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, long, Strigi::IndexWriter&, Strigi::StreamAnalyzer&)'" you probably have an outdated version of strigi installed by your distro. By the way, after update the strigi, you must recompile kdelibs for a new libkio.so.
* If you get the issue "can't find REQUIRED package Blitz", install qimageblitz4 and qimageblitz-dev
* If you get an error "class QWebFrame' has no member named 'contentsSize'" you need to upgrade your Qt
* If you have troubles building networkmanager-0.6, check if you have networkmanager-dev and libnm-util-dev installed
* If you get during cmake
Please set the following variables:
CLUCENE_LIBRARY_DIR (ADVANCED)
Make sure you have clucene installed and clucene-devel. If necessary, get the source from sourceforge and compile it. If you have SUSE and an x64 installation, you need to make cmake aware your library path is /usr/lib64, not /usr/lib. Do this with
cmake -DLIB_SUFFIX=64 .
* If you get an error saying your soprano libraries are too old, but you've installed them under kdesupport, check to see if your build is using your system libraries instead. If so, then set:
CMAKE_LIBRARY_PATH=/home/kde-devel/kde/lib:$CMAKE_LIBRARY_PATH
CMAKE_INCLUDE_PATH=/home/kde-devel/kde/include:$CMAKE_INCLUDE_PATH

and delete the CMakeCache.txt in your build directory.
== Issues building kdepimlibs ==
If you have trouble compiling kdepimlibs:
* the cmakekde command may require a later version of the gpgme library. This is available from the project's web site: http://www.gnupg.org/download/index.html - please note that the build of gpgme also requires libgpg-error, also available from the same location. Both libraries are installed by the "./configure", "make" and "sudo make install" sequence, with the gpgme library configured with the additional "--with-gpg-error-prefix" parameter. You may need to overwrite your existing "/usr/bin/gpgme-config" file with the newer version for the kdepimlibs to pick up the new install.
* if cmake complains about missing akonadi headers, (CMake Error: Could not find Akonadi includes. or something similiar), then you lack the akonadi package which can be found in the kdesupport module. Since the kdesupport as a whole is quite large it is recommended that you selectively download the packages you need instead of fetching the entire kdesupport module.Akonadi relies on automoc, so we have to install it prior to building akonadi. The Automoc module can also be found in kdesupport.

=== The Recipe for Automoc ===
cd
cs
mkdir kdesupport && cd kdesupport
svn checkout svn://anonsvn.kde.org/home/kde/trunk/kdesupport/automoc
cd automoc
cmakekde

=== The Recipe for Akonadi ===
cd
cs
cd kdesupport
svn checkout svn://anonsvn.kde.org/home/kde/trunk/kdesupport/akonadi
cd akonadi
cmakekde

== Running programs ==

* If you get
KUniqueApplication: Cannot find the D-Bus session server
make sure you can access the display, e.g. type
xclock
then a clock must appear on the screen. If it does and the error persists, start your shell using
dbus-launch xterm
and start your program in there.

* If you get something like
Error: standard icon theme "oxygen" not found!

ASSERT: "!isEmpty()" in file /home/kde-devel/qt-copy/include/QtCore/../../src/corelib/tools/qlist.h, line 245
Aborted (core dumped)
You need to install kdebase - see above. It is enough to install the "runtime" directory from kdebase.

== General troubleshooting ==

What can happen over time, after some <tt>svn up</tt> commands, is that some of the tools used in the KDE build chain change their output format. For example, <tt>kcfg</tt> files are read by <tt>kconfig_compiler</tt> to produce configuration dialogs. CMake cannot detect those changes, and the compilation might fail. A workaround is to always force a re-generation of all such files:
find $KDE_SRC/KDE/kdebase -name "*.kcfg" | xargs touch
The same applies to <tt>ui</tt> files as produced by Qt designer.

=== Locked sessions ===
When installing KDE 4 as a user, one will not be able to unlock a locked session. To work around this issue you can either:
su chown root.root $KDEDIR/lib/kde4/libexec/kcheckpass
or
chmod 755 $KDEDIR/lib/kde4/libexec/kcheckpass

Also you have to add a "kde" service in /etc/pam.d/ folder

For example for RH/Fedora based distros:
<code>
#%PAM-1.0
auth include system-auth
account include system-auth
password include system-auth
session include system-auth
</code>

while for debian/Kubuntu (requires having libpam-dev installed while building kdebase):
<code>
# Standard Un*x authentication.
@include common-auth
@include common-account
@include common-session
@include common-password
</code>