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

Revision as of 00:22, 3 March 2007 by Aseigo (Talk | contribs)

Jump to: navigation, search

Contents

cs and cb versus cd

If you're reading the article and wondering who in their right mind would misspell the cd command as cs so many times, you need to 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. Make sure it's actually a mistake before 'fixing' the article by changing cs or cb to cd. Otherwise it'll just be reverted. --Mpyne 21:23, 28 February 2007 (CET)

~/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 produce 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)

KDElibs.com and developernew.kde.org coexistence

Regarding content from kdelibs.com, see User_talk:Jstaniek#KDElibs.com_and_developernew.kde.org_coexistence --jstaniek 18:10, 11 January 2007 (CET)

Apidox

Can anybody please add instructions on how to build the apidox? I managed to do this for kdelibs, but not for kdepim or kdepimlibs.

TMG 16:12, 26 January 2007 (CET)


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal