Talk:Installing third party softwares in terminal/Build/KDE4: Difference between revisions

From KDE TechBase
(remove all the issues that have been dealt with.)
Line 2: Line 2:


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. --[[User:Mpyne|Mpyne]] 21:23, 28 February 2007 (CET)
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. --[[User:Mpyne|Mpyne]] 21:23, 28 February 2007 (CET)
'''Comment:''' I just fell into the same trap and then tried to correct this in the wiki. I think the main reason for the confusion regarding cs/cb vs. cd is that most users (myself included) just copy&paste the commands and then wonder when the commands fail due to missing src & build directories. My first guess was 'well, there's a typo in the cd command.' I suggest adding a "mkdir -p" for src and build to the .bashrc provided on the wiki page.


== ~/install ==
== ~/install ==
Line 13: Line 11:
-- It is impossible to order the include directories.
-- 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.
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.
You may not experience any problems when installed like I advise not to, however I have and you might too in some typical situations.
Line 20: Line 18:


http://developer.kde.org/build/trunk.html
http://developer.kde.org/build/trunk.html
== Platform Independence ==
We should provide multiple versions of these instructions based on which OS the user wishes to compile on. Right now the windows instructions are on kdelibs.com and I don't know of any Mac instructions. [[User:Mattr|Mattr]] 17:42, 26 December 2006 (CET)
there are mac instructions and the instruction kdelibs.com will be moving here once things are more settled in the win32 build. i've already talked to jstaniek about this some time ago --[[User:Aseigo|Aseigo]] 00:01, 3 March 2007 (CET)
== Excluding Qt examples from building ==
In a couple of build tutorials I've seen various ways to build only the src and tools directories (like 'make sub-src sub-tools'). Should we mention this here (since it does speed up compiling a lot by skipping the examples etc)? -- milliams 22:12, 30 December 2006 (CET)
: I exclude the examples as well, and the magic ./configure option is: '''-nomake examples'''<br>--[[User:Dhaumann|Dhaumann]] 17:44, 4 January 2007 (CET)


== Install CMake modules local ==
== Install CMake modules local ==
Line 43: Line 29:


--[[User:Eliasp|Eliasp]] 15:44, 4 January 2007 (CET)
--[[User:Eliasp|Eliasp]] 15:44, 4 January 2007 (CET)


== KDElibs.com and developernew.kde.org coexistence ==
== KDElibs.com and developernew.kde.org coexistence ==
Regarding content from kdelibs.com, see [[User_talk:Jstaniek#KDElibs.com_and_developernew.kde.org_coexistence]]
Regarding content from kdelibs.com, see [[User_talk:Jstaniek#KDElibs.com_and_developernew.kde.org_coexistence]]
--[[User:Jstaniek|jstaniek]] 18:10, 11 January 2007 (CET)
--[[User:Jstaniek|jstaniek]] 18:10, 11 January 2007 (CET)
== Install prefix ==
I don't know if I missed something but shouldn't the build instructions for kdelibs, kdepimlibs and kdebase be followed by make && make install? Furthermore, the cmake command should ideally be called with the -DCMAKE_INSTALL_PREFIX=$KDEDIR cmdline argument to let a user install into the local ~/kde directory so no root permissions are required and /usr/local doesn't get polluted.


== Apidox ==
== Apidox ==
Line 56: Line 38:


[[User:TMG|TMG]] 16:12, 26 January 2007 (CET)
[[User:TMG|TMG]] 16:12, 26 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
== 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
--[[User:141.35.185.149|141.35.185.149]] 17:34, 2 March 2007 (CET)
== qt-copy without examples? ==
My system is mainly compiling the qt-copy examples, and I wonder if that is really needed. If not, is there a configure switch to prevent make to compile the examples?
--[[User:141.35.185.149|141.35.185.149]] 17:37, 2 March 2007 (CET)
:The same is true for the demos, btw. --[[User:141.35.185.149|141.35.185.149]] 18:14, 2 March 2007 (CET)

Revision as of 23:22, 2 March 2007

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)

Retrieved from "https://techbase.kde.org/index.php?title=Talk:Installing_third_party_softwares_in_terminal/Build/KDE4&oldid=8567"