Talk:Installing third party softwares in terminal/Build/KDE4

Q: What is cs and cb?

A: This is not a typo. Read the article about setting up your .bashrc. Both cs and cb are bash functions, used to change to the KDE source directory and KDE build directory respectively.

Q: Are there build instructions for other OS?

A: Actually yes, for Mac OS X. There also is kdelibs.com (see also here) which will be merged into this wiki in the future.

Q: How can I exclude qt-copy examples from building?

A: Append the ./configure option: -nomake examples. This is even the default now.

Q: Isn't the install prefix, make and make install missing for modules like kdelibs and kdebase?

A: No. The shell function cmakekde handels this, have a look at the file .bashrc.

Q: How can I generate API Documentation for other modules?

A: Try the following code, replacing <modulename> with your desired module:

cs
mkdir -p apidox
cs apidox
../kdelibs/doc/api/doxygen.sh ../<modulename>/

Notes: ~/install

When installing KDE4, I strongly recommend installing all tools (like dbus and cmake) and kde packages into the same place, e.g. ~/install. Qt is the only exception.

The reason for this is because if you install some packages to ~/kde and some to /usr/local and maybe one in /usr then cmake will generate errors like:

-- It is impossible to order the include directories.

This is not a fatal error, so you will still be able to compile, but you will possibly be using the wrong versions of libraries and this will product problems that are very hard to diagnose.

You may not experience any problems when installed like I advise not to, however I have and you might too in some typical situations.

Please see:

http://developer.kde.org/build/trunk.html

Install CMake modules local

The CMake modules should be installed local into ~/install/cmake/modules or similar. When following the current instructions 6.1: Install additional CMake modules, it's impossible to do a non-root installation, because "kdelibs/cmake/modules/cmake_install.cmake" wants to install the modules to "/cmake/modules". (I didn't install CMake local, because my system already provided CMake > 2.4.3).

I've already tried to do this, fiddling around with CMAKE_MODULE_PATH and DATA_INSTALL_DIR but couldn't get it working.

Does anybody know how to do this properly?

--Eliasp 15:44, 4 January 2007 (CET)

Set up D-Bus

Doesn't it have to be "--localstatedir=$HOME/var" instead of "--localstatedir=/var" when configuring Dbus? When i use the latter, i get a permission denied

True, that looks weird. Maybe someone can have a look? --Dhaumann 11:02, 6 March 2007 (CET)

Fixes needed

There are still some places where the code is not according to the explanation or the other way around:

• d-bus: there is a 'cs' at the beginning, but the explanation says line 1 is the wget line
• cmake: the code says 'cs' while the explanation says home directory
• qt-copy: the code says 'cs' while the explanation says home directory

--141.35.185.149 17:34, 2 March 2007 (CET)

• qt-copy: Should we pass the -debug flag? Doesn't Qt install debug information separately by default anyways? Or is that just in the snapshot? --Mpyne

Fixes in qt-copy (consistency) recipe: `cd` instead of `cs` to match .bashrc example's QTDIR. Deleted `make install` as "You should not run 'make install'" ;)