Translations talk:Installing third party softwares in terminal/Set up KDE 4 for development
What benefits does ssh -X kde-devel@localhost have over su - kde-devel? The question is directed mainly at tstaerk. ;) Logixoul 00:54, 5 January 2007 (CET)
Have you considered using sux instead of "ssh -X" or "su - kde-devel && export DISPLAY=:0 && xhost +localhost:kde-devel" I see it easier and more convient. Kebianizao 18:40, 7 July 2007 (CET)
IIRC, $KDEDIR is not used anymore for some weeks now. It's $KDEDIRS now. Right? --Dhaumann 19:35, 27 January 2007 (CET)
- Yes, but as used in this tutorial it's just a regular environment variable used to fill in the $PREFIX in other env vars. Perhaps it should be renamed to $KDE_PREFIX or something? --Aseigo 00:55, 30 January 2007 (CET)
- How about $KDEBASEDIR? --126.96.36.199 08:43, 30 January 2007 (CET)
- Ah ok. Then let's keep KDEDIR, it's short and meaningful. --Dhaumann 09:29, 30 January 2007 (CET)
Can a note be added on how to change the Xephyr keyboard layout? I tried several options already but always end up with the default qwerty layout :( --tbscope 15:06, 24 February 2007 (CET)
Start Xephyr with the +kb option which enables the xkb extension. Then choose your keyboard layout in KDE as usual (System Settings/Regional&Language/Keyboard Layout) --BenjieMouse 12:35, 19 July 2008 (CEST)
The default screen size for Xephyr is 640x480 which is not enough for using KDE. I propose adding the parameter -screen 1024x768x16 for example. --Kebianizao 19:45, 10 July 2007 (CET)
Wouldn't it be helpful, to post a hint, that the installation of kdesdk is very useful? --Lucas-r2d2 18:37, 3 May 2007 (CEST)
- Well, probably yes (I don't use it myself). Please add it to the page (I'd say same level as KDevelop/KBugBuster/...). Explain how to install it (if that is much different from kdebase) and explain how to use the programs included there and why they are useful. Make sure there is no overlap with this page. TMG 17:16, 5 May 2007 (CEST)
I followed the chapter about kdevelop, nice work. Especially: - you tell the reader what to do - you tell him why to do this - your language is clear, e.g. "Now you should be able to start KDevelop by typing start3app kdevelop. Do that now."
I really like this tutorial and it worked for me. Thanks for the tutorial.
- All menu items you name do not exist for me. I am using the latest kdevelop version from 3.5 branch, 3.3.5 (which is too minor according to you).
- $KDE_SRC/KDE/kdelibs/kdelibs-apidocs/index.html does not exist for me. make apidox is not possible.
--Tstaerk 09:25, 21 December 2007 (CET)
Problem: Kdevelop codecompletetion for KDE libs
Having problems getting the codecompletion to work for kde. Qt4 works just fine.
Tried to tell the importer to import every file in /usr/include/KDE which it does, but codecompletetion won't work.
Do this problem have anything to do with the fact that KDE includes look like this (in this case /usr/include/KDE/KApplication):
Also tried to download the newest KDElibs (4.0.1), but the files in the "includes" dir looks exactly the same as those in /usr/include/KDE
I use a temporary solution: I import every k*.h file from /usr/include which seems to get most of the kde header files.
--188.8.131.52 10:52, 12 February 2008 (CET)
- The includes in /usr/include/KDE are just forward includes, which the KDevelop parser does not understand. The real includes are indeed directly in /usr/include. I suggest telling KDevelop to parse the files in the kdelibs source directory, which usually is $KDE_SRC/KDE/kdelibs if you've followed the Techbase guide to build.
- If you don't have the source, then I guess the only thing you can do is to import every k*.h file from /usr/include, but that will miss many files. --TMG 19:01, 12 February 2008 (CET)