Difference between revisions of "Development/FAQs/Technical FAQ"

Jump to: navigation, search
m (Text replace - "</code>" to "</syntaxhighlight>")
(Marked this version for translation)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:I18n/Language Navigation Bar|Development/FAQs/Technical FAQ}}
+
<languages />
 +
<translate>
 +
<!--T:106-->
 
{{improve|The build system has changed in KDE4.}}
 
{{improve|The build system has changed in KDE4.}}
==How do I start a new application?==
 
  
 +
==How do I start a new application?== <!--T:2-->
 +
 +
<!--T:3-->
 
The easiest way is to use kdesdk/kapptemplate to generate the CMakeLists.txt. Or you can just copy a CMakeLists.txt from another app and install it in a new toplevel directory of existing KDE sources. Or you can start the old way, from scratch.  
 
The easiest way is to use kdesdk/kapptemplate to generate the CMakeLists.txt. Or you can just copy a CMakeLists.txt from another app and install it in a new toplevel directory of existing KDE sources. Or you can start the old way, from scratch.  
  
==What is plasma, kpart, kio, kdeinit, ...==
+
==What is plasma, kpart, kio, kdeinit, ...== <!--T:4-->
Check TechBase, especially the [[Development/Architecture|architecture documents]]. Check also the kde book.
+
  
==Do I really need to use kpart?==
+
<!--T:5-->
 +
Check TechBase, especially the [[Special:myLanguage/Development/Architecture|architecture documents]]. Check also the kde book.
  
 +
==Do I really need to use kpart?== <!--T:6-->
 +
 +
<!--T:7-->
 
Well, you are not forced to but it is a lot better. KPart allows powerful code reuse. Given how simple it is to use the technology and how widely it is deployed, it is a shame not to use it if you can.  
 
Well, you are not forced to but it is a lot better. KPart allows powerful code reuse. Given how simple it is to use the technology and how widely it is deployed, it is a shame not to use it if you can.  
  
==How do I write a CMakeLists.txt?==
+
==How do I write a CMakeLists.txt?== <!--T:8-->
Please follow this [[Development/Tutorials/CMake|CMake tutorial]].
+
 
 +
<!--T:9-->
 +
Please follow this [[Special:myLanguage/Development/Tutorials/CMake|CMake tutorial]].
 +
 
 +
==What targets are available to make?== <!--T:10-->
  
==What targets are available to make?==
+
<!--T:11-->
 
*all: the default target (the one you get when typing "make").  
 
*all: the default target (the one you get when typing "make").  
 
*clean: removes all the generated files  
 
*clean: removes all the generated files  
Line 27: Line 38:
 
*check: compiles the test programs (i.e. those defined with check_PROGRAMS). It is even possible to actually run some tests during "make check", see kdelibs/arts/tests/Makefile.am  
 
*check: compiles the test programs (i.e. those defined with check_PROGRAMS). It is even possible to actually run some tests during "make check", see kdelibs/arts/tests/Makefile.am  
  
==I have a checkout of SVN, there is no configure and no Makefile?==
+
==I have a checkout of SVN, there is no configure and no Makefile?== <!--T:12-->
 +
 
 +
<!--T:13-->
 
Use make -f Makefile.cvs It will run all the Makefile generation steps  
 
Use make -f Makefile.cvs It will run all the Makefile generation steps  
  
==How can I temporarily exclude certain directories from build?==
+
==How can I temporarily exclude certain directories from build?== <!--T:14-->
 +
 
 +
<!--T:15-->
 
While hacking a program it might be useful to exclude certain directories from build that would otherwise be recompiled, but don't actually need to be.
 
While hacking a program it might be useful to exclude certain directories from build that would otherwise be recompiled, but don't actually need to be.
 
Also, if you checked out source code that didn't compile and you don't have the time or knowledge to fix the error you might want to turn off compilation of the directory alltogether.
 
Also, if you checked out source code that didn't compile and you don't have the time or knowledge to fix the error you might want to turn off compilation of the directory alltogether.
 
There are two cases. Toplevel directories, and subdirectories. For toplevel directories you can simply erase them (or not check them out).  
 
There are two cases. Toplevel directories, and subdirectories. For toplevel directories you can simply erase them (or not check them out).  
  
If for some reason you don't want to do that, you can also set <tt>DO_NOT_COMPILE="someapp"</tt> before calling configure, this will make configure skip "someapp". To only compile very few toplevel dirs, instead of using <tt>DO_NOT_COMPILE</tt> to exclude most of them, you can list in a file named 'inst-apps', at the toplevel, the toplevel subdirs you want to compile.  
+
<!--T:16-->
 +
If for some reason you don't want to do that, you can also set <code>DO_NOT_COMPILE="someapp"</code> before calling configure, which will make configure skip "someapp". To only compile very few toplevel dirs, instead of using <code>DO_NOT_COMPILE</code> to exclude most of them, you can list in a file named ''inst-apps'', at the toplevel, the toplevel subdirs you want to compile.  
 +
 
 +
<!--T:17-->
 
To turn off compilation of any directory, including subdirectories, you have to modify the Makefile or Makefile.am files. Makefile.am is not recommended because that file is in KDE Subversion and you could accidentally commit your changes. So we'll modify the Makefile instead here:
 
To turn off compilation of any directory, including subdirectories, you have to modify the Makefile or Makefile.am files. Makefile.am is not recommended because that file is in KDE Subversion and you could accidentally commit your changes. So we'll modify the Makefile instead here:
  
Open the Makefile in the directory immediately above the directory you want to exclude in a text editor and look for a variable <tt>SUBDIRS</tt>. It will often look somewhat like
+
<!--T:18-->
 +
Open the Makefile in the directory immediately above the directory you want to exclude in a text editor and look for a variable <code>SUBDIRS</code>. It will often look somewhat like
  
SUBDIRS = share core ui . proxy taskmanager taskbar applets extensions data
+
<!--T:19-->
 +
{{Input|1=SUBDIRS = share core ui . proxy taskmanager taskbar applets extensions data}}
  
 +
<!--T:20-->
 
Just remove the directory that you want to exclude and save your file. A new make will skip the directory you just removed.
 
Just remove the directory that you want to exclude and save your file. A new make will skip the directory you just removed.
  
 +
<!--T:21-->
 
Sometimes you'll have to look harder because the SUBDIRS variable consists of a number of other variables:
 
Sometimes you'll have to look harder because the SUBDIRS variable consists of a number of other variables:
  
SUBDIRS = $(COMPILE_FIRST) $(TOPSUBDIRS) $(COMPILE_LAST)  
+
<!--T:22-->
 +
<code>SUBDIRS = $(COMPILE_FIRST) $(TOPSUBDIRS) $(COMPILE_LAST) </code>
  
Here you have to find the <tt>COMPILE_FIRST</tt>, <tt>TOPSUBDIRS</tt> and <tt>COMPILE_LAST</tt> variables. One of those contains the dir you want to exclude. Remove the directory where you find it and save the Makefile again.
+
<!--T:23-->
 +
Here you have to find the <code>COMPILE_FIRST</code>, <code>TOPSUBDIRS</code> and <code>COMPILE_LAST</code> variables. One of those contains the dir you want to exclude. Remove the directory where you find it and save the Makefile again.
 
To undo your changes you can either regenerate the Makefile from scratch or revert to an older backup (you did make one, did you? :-).
 
To undo your changes you can either regenerate the Makefile from scratch or revert to an older backup (you did make one, did you? :-).
 
To regenerate a Makefile, just make force-reedit.
 
To regenerate a Makefile, just make force-reedit.
  
 +
<!--T:24-->
 
You can also copy the original line in the file when editing and make it a comment by prefixing a '#' in front of it. Then undoing the change is as easy as making the modified line a comment and removing the comment in the original line.
 
You can also copy the original line in the file when editing and make it a comment by prefixing a '#' in front of it. Then undoing the change is as easy as making the modified line a comment and removing the comment in the original line.
  
==What are the various compilation options?==
+
==What are the various compilation options?== <!--T:25-->
--enable-debug
+
  
Add debug symbols, disable optimisations and turns logging of kdDebug() on.  
+
<!--T:26-->
 +
<code> --enable-debug</code>
 +
: Add debug symbols, disable optimisations and turns logging of kdDebug() on.  
  
--disable-debug
+
<!--T:27-->
 +
<code>--disable-debug</code>
 +
: The opposite of the previous one: enable optimisations and turns kdDebug() logging off.
  
The opposite of the previous one: enable optimisations and turns kdDebug() logging off.
+
<!--T:28-->
 
+
<code> --enable-final</code>
--enable-final
+
: Concatenates all .cpp files into one big .all_cpp.cpp file, and compiles it in one go, instead of compiling each .cpp file on its own. This makes the whole compilation much faster, and often leads to better optimised code, but it also requires much more memory. And it often results in compilation errors when headers included by different source files clash one with the other, or when using c static functions with the same name in different source files.  
 
+
Concatenates all .cpp files into one big .all_cpp.cpp file, and compiles it in one go, instead of compiling each .cpp file on its own. This makes the whole compilation much faster, and often leads to better optimised code, but it also requires much more memory. And it often results in compilation errors when headers included by different source files clash one with the other, or when using c static functions with the same name in different source files.  
+
 
This is a good thing to do at packaging time, but of course not for developers, since a change in one file means recompiling everything.
 
This is a good thing to do at packaging time, but of course not for developers, since a change in one file means recompiling everything.
  
--disable-fast-perl
+
<!--T:29-->
 +
<code> --disable-fast-perl</code>
 +
: By default KDE uses perl instead of sh and sed to convert Makefile.in into Makefile. This is an addition to autoconf done by Michael Matz. You can use this option to disable this but it is a lot slower.
  
By default KDE uses perl instead of sh and sed to convert Makefile.in into Makefile. This is an addition to autoconf done by Michael Matz. You can use this option to disable this but it is a lot slower.
+
==Which compile option do you recommend?== <!--T:30-->
  
==Which compile option do you recommend?==
+
<!--T:31-->
 
If you are a developer, you should definitely compile Qt and KDE with --enable-debug. You will then be able to debug your program even inside Qt and KDE function calls.  
 
If you are a developer, you should definitely compile Qt and KDE with --enable-debug. You will then be able to debug your program even inside Qt and KDE function calls.  
If you are just a user, you can still use --enable-debug. KDE will occupy more space on your hard disk but it won't slow down your desktop. The advantage is that you get stack trace when an application crash. If you can reproduce a crashing behaviour, go to bugs.kde.org, check that your bug doesn't exist yet and submit it. It will help us improve kde.
+
If you are just a user, you can still use --enable-debug. KDE will occupy more space on your hard disk but it won't slow down your desktop. The advantage is that you get stack trace when an application crashes. If you can reproduce a crashing behaviour, go to bugs.kde.org, check that your bug doesn't exist yet and submit it. It will help us improve kde.
 
For Qt, the compilation options are explained in qt-copy/README.qt-copy.
 
For Qt, the compilation options are explained in qt-copy/README.qt-copy.
  
==Tips to increase compilation speed?==
+
==Tips to increase compilation speed?== <!--T:32-->
See --enable-final above :) . "make final" uses the all-in-one-file trick in the current directory even if --enable-final wasn't used, and "make no-final" does a normal compilation in the current directory even if --enable-final was used.  
+
 
 +
<!--T:33-->
 +
See ''--enable-final'' above :) . ''make final'' uses the all-in-one-file trick in the current directory even if --enable-final wasn't used, and ''make no-final'' does a normal compilation in the current directory even if --enable-final was used.  
 
Include your moc files! Header files declaring a QObject descendant have to be run through moc to produce a .moc file. This .moc file has to be compiled, for which two possibilities exists: compile it separately, or #include it in the C++ file implementing that above mentioned class. The latter is more efficient in term of compilation speed. BTW, kdesdk/scripts/includemocs does this automatically.
 
Include your moc files! Header files declaring a QObject descendant have to be run through moc to produce a .moc file. This .moc file has to be compiled, for which two possibilities exists: compile it separately, or #include it in the C++ file implementing that above mentioned class. The latter is more efficient in term of compilation speed. BTW, kdesdk/scripts/includemocs does this automatically.
 
Buy more ram, a faster machine and another processor. On a bi-PIII 866 MHz with 1GB of RAM, kde compiles at a decent speed :-)))
 
Buy more ram, a faster machine and another processor. On a bi-PIII 866 MHz with 1GB of RAM, kde compiles at a decent speed :-)))
  
==There is a STRIP variable set in the Makefile but it doesn't seem to be used?==
+
==There is a STRIP variable set in the Makefile but it doesn't seem to be used?== <!--T:34-->
 +
 
 +
<!--T:35-->
 
The strip is done at install. To use it, use "make install-strip" instead of "make install".  
 
The strip is done at install. To use it, use "make install-strip" instead of "make install".  
  
==What indentation should I use?==
+
==What indentation should I use?== <!--T:36-->
 +
 
 +
<!--T:37-->
 
If you are working on an existing application, respect the author's indentation. Else, you can use whatever indentation you like.  
 
If you are working on an existing application, respect the author's indentation. Else, you can use whatever indentation you like.  
  
==What is the difference between i18n and I18N_NOOP?==
+
==What is the difference between i18n and I18N_NOOP?== <!--T:38-->
 +
 
 +
<!--T:39-->
 
If you do
 
If you do
QString translatedStuff = i18n("foobar");
+
<code>QString translatedStuff = i18n("foobar");</code> translatedStuff will contain the translation of "foobar", while for <code> const char *markedStuff = I18N_NOOP("foobar");</code> <tt>markedStuff</tt> will still contain literal "foobar", but translators will know you want "foobar" translated so you can later on do <code>QString translatedStuff = i18n(markedStuff);</code> and get the translation of "foobar", which wouldn't work without that I18N_NOOP.
 +
So, normally you want to just use i18n(), but in cases where you absolutely need to pass something untranslated, but still need to translate it later or in the case that you have something to be translated before the KInstance exists, use <code>I18N_NOOP()</code>.
  
translatedStuff will contain the translation of "foobar", while for
+
==I get "virtual tables error"?== <!--T:40-->
  
const char *markedStuff = I18N_NOOP("foobar");
+
<!--T:41-->
 
+
<tt>markedStuff</tt> will still contain literal "foobar", but translators will know you want "foobar" translated so you can later on do QString translatedStuff = i18n(markedStuff); and get the translation of "foobar", which wouldn't work without that I18N_NOOP.
+
So, normally you want to just use i18n(), but in cases where you absolutely need to pass something untranslated, but still need to translate it later or in the case that you have something to be translated before the KInstance exists, use <tt>I18N_NOOP()</tt>.
+
 
+
==I get "virtual tables error"?==
+
 
This often comes from the moc files not being in sync with the sources, or not linked at all. Check that you are running the right moc. 'which moc' will tell it. Regenerate your moc files (make force-reedit; make clean; make).  
 
This often comes from the moc files not being in sync with the sources, or not linked at all. Check that you are running the right moc. 'which moc' will tell it. Regenerate your moc files (make force-reedit; make clean; make).  
  
==I have added Q_OBJECT to myClassHeader.h but no moc files is generated?==
+
==I have added Q_OBJECT to myClassHeader.h but no moc files is generated?== <!--T:42-->
 +
 
 +
<!--T:43-->
 
You need am_edit to reparse your Makefile.am to generate the correct Makefile. If it's the first Q_OBJECT you're using in this directory, you'll need to re-run Makefile.cvs or create_makefile from kdesdk/scripts. Otherwise, you can simply run "make force-reedit".
 
You need am_edit to reparse your Makefile.am to generate the correct Makefile. If it's the first Q_OBJECT you're using in this directory, you'll need to re-run Makefile.cvs or create_makefile from kdesdk/scripts. Otherwise, you can simply run "make force-reedit".
  
==To go quicker, I have coded my whole class in a cpp file, how do I get the moc files generated?==
+
==To go quicker, I have coded my whole class in a cpp file, how do I get the moc files generated?== <!--T:44-->
 +
 
 +
<!--T:45-->
 
Hmm, don't do that, if some of the classes use the Q_OBJECT macro. Maybe METASOURCES=file.cpp might work for moc files though.  
 
Hmm, don't do that, if some of the classes use the Q_OBJECT macro. Maybe METASOURCES=file.cpp might work for moc files though.  
  
==I have developed a kpart (or a plugin). I don't want to install it yet because it is not finished but I need that KDE finds it when I request it using KTrader or KLibLoader. How do I do that?==
+
==I have developed a kpart (or a plugin). I don't want to install it yet because it is not finished but I need that KDE finds it when I request it using KTrader or KLibLoader. How do I do that?== <!--T:46-->
 +
 
 +
<!--T:47-->
 
KDE searches its libraries in $KDEDIR/lib and in the lib directory of all the components of $KDEDIRS (note the additional 'S', this different from $KDEDIR). So, while you are still developing your library and don't want to install it, you can use this trick:  
 
KDE searches its libraries in $KDEDIR/lib and in the lib directory of all the components of $KDEDIRS (note the additional 'S', this different from $KDEDIR). So, while you are still developing your library and don't want to install it, you can use this trick:  
cd to your development directory, the one where your library is built.
 
Set up KDEDIRS so that it include your development directory: export KDEDIRS=`pwd`:$KDEDIR
 
Create a pseudo lib directory where KDE should find your component: ln -s .libs lib (all the objects and libraries are built in the .libs directory).
 
Run kbuildsycoca to inform KDE that it KDEDIRS has changed.
 
  
 +
<!--T:48-->
 +
: cd to your development directory, the one where your library is built. <br />
 +
: Set up KDEDIRS so that it include your development directory: export KDEDIRS=`pwd`:$KDEDIR <br />
 +
: Create a pseudo lib directory where KDE should find your component: ln -s .libs lib (all the objects and libraries are built in the .libs directory). <br />
 +
: Run kbuildsycoca to inform KDE that it KDEDIRS has changed.
 +
 +
<!--T:49-->
 
Now, KDE should find your library when using KTrader or KLibLoader.  
 
Now, KDE should find your library when using KTrader or KLibLoader.  
  
==How can I install additional KDE stuff when I am not root?==
+
==How can I install additional KDE stuff when I am not root?== <!--T:50-->
If want to install your application privately, configure it with another prefix: for $HOME/kdeprefix, use configure --prefix=$HOME/kdeprefix. Then let KDE know about this prefix: set KDEDIRS to $HOME/kdeprefix:$KDEDIR. To make KDE aware of new prefixes, one can also edit /etc/kderc and add
+
  
[Directories]
+
<!--T:51-->
prefixes=/the/new/prefix
+
If want to install your application privately, configure it with another prefix: for $HOME/kdeprefix, use <code>configure --prefix=$HOME/kdeprefix</code>. Then let KDE know about this prefix: set KDEDIRS to <tt>$HOME/kdeprefix:$KDEDIR</tt>. To make KDE aware of new prefixes, one can also edit /etc/kderc and add
  
 +
<!--T:52-->
 +
{{Input|1=[Directories]
 +
prefixes=/the/new/prefix}}
 +
 +
<!--T:53-->
 
but this doesn't answer this specific question ;-)
 
but this doesn't answer this specific question ;-)
 
Make sure to run "kbuildsycoca" after setting the new KDEDIRS.
 
Make sure to run "kbuildsycoca" after setting the new KDEDIRS.
  
==My kpart lib is not listed when I request it with KTrader==
+
==My kpart lib is not listed when I request it with KTrader== <!--T:54-->
 +
 
 +
<!--T:55-->
 
The mimetype database must be rebuilt when you install new services (such as applications or parts). In theory this happens by itself (kded is watching those directories), but in doubt, run "kbuildsycoca".
 
The mimetype database must be rebuilt when you install new services (such as applications or parts). In theory this happens by itself (kded is watching those directories), but in doubt, run "kbuildsycoca".
The best way to debug trader-related problems is to use ktradertest: cd kdelibs/kio/tests; make ktradertest, then run ./ktradertest to see how to use it.
+
The best way to debug trader-related problems is to use <code>ktradertest: cd kdelibs/kio/tests; make ktradertest</code>, then run <code>./ktradertest</code> to see how to use it.
 +
 
 +
==I changed something in kdelibs, installed the new lib, but new KDE apps don't seem to use it?== <!--T:56-->
  
==I changed something in kdelibs, installed the new lib, but new KDE apps don't seem to use it?==
+
<!--T:57-->
 
The solution is simple: start new apps from a command line, then they will use the new lib.
 
The solution is simple: start new apps from a command line, then they will use the new lib.
  
 +
<!--T:58-->
 
The reason is that applications started by other KDE applications (kicker, minicli, konqueror, etc.) are started via kdeinit, which loads the libs when KDE starts. So the "old" version of the libs keep being used. But if you want kdeinit to start using the new libs, simply restart it. This is done by typing kdeinit in a terminal.  
 
The reason is that applications started by other KDE applications (kicker, minicli, konqueror, etc.) are started via kdeinit, which loads the libs when KDE starts. So the "old" version of the libs keep being used. But if you want kdeinit to start using the new libs, simply restart it. This is done by typing kdeinit in a terminal.  
  
 +
<!--T:59-->
 
This is necessary if you can't start things from the command line - e.g. for a kioslave. If you change something in kio, you need to restart kdeinit and kill the running kioslave, so that a new one is started.
 
This is necessary if you can't start things from the command line - e.g. for a kioslave. If you change something in kio, you need to restart kdeinit and kill the running kioslave, so that a new one is started.
  
==I'm developing both a KPart and a standalone application, how do I avoid duplicated code?==
+
==I'm developing both a KPart and a standalone application, how do I avoid duplicated code?== <!--T:60-->
 +
 
 +
<!--T:61-->
 
Apps are often tempted to link to their part because they of course have much functionality in common. However this is wrong for the reasons below.
 
Apps are often tempted to link to their part because they of course have much functionality in common. However this is wrong for the reasons below.
 +
 +
<!--T:62-->
 
A lib is something you link to, a module is something you dlopen. You can't dlopen a lib ; you can't link to a module.
 
A lib is something you link to, a module is something you dlopen. You can't dlopen a lib ; you can't link to a module.
 +
 +
<!--T:63-->
 
A lib has a version number and is installed in $libdir (e.g. $KDEDIR/lib) a module doesn't have a version number (in its name), it's more like a binary (we don't have konqueror-1.14.23 either :), and is installed into kde_moduledir (e.g. $KDEDIR/lib/kde3) (which means it's not in the search path for ld.so, so this breaks on systems without -rpath).
 
A lib has a version number and is installed in $libdir (e.g. $KDEDIR/lib) a module doesn't have a version number (in its name), it's more like a binary (we don't have konqueror-1.14.23 either :), and is installed into kde_moduledir (e.g. $KDEDIR/lib/kde3) (which means it's not in the search path for ld.so, so this breaks on systems without -rpath).
 +
 +
<!--T:64-->
 
If you didn't understand the above, don't worry. The point is: you should NOT make your application link to your (or any other) KPart, nor any other kind of dlopened module.
 
If you didn't understand the above, don't worry. The point is: you should NOT make your application link to your (or any other) KPart, nor any other kind of dlopened module.
The solutions
 
let the app dlopen the part. This is what KOffice does. However this limits the app to the very limited ReadOnlyPart/ReadWritePart API. Keep in mind that you can't call a non-virtual method whose implementation you don't link to. The solution is to define a ReadWritePart-derived class (like we have in koffice: KoDocument), with new virtual methods. Either this derived class has code (and you need a lib shared by the app and the part, see point 2 below), or an abstract interface (header file only) is enough. You can also use known interfaces to child objects of the part instead of changing the base class of the part itself - this is the solution used by e.g. KParts::BrowserExtension.
 
define a common library with the common classes and let both the part and the app use it. That library can be noinst_ or lib_, both work. In the first case the compiled object code is duplicated, in the second case a real versioned lib will be installed. The idea here is that the part itself is not available to the app, but instead the part is a very thin wrapper around the same classes as the app uses. Only KParts-specific stuff remains in the part.
 
  
==What is the best way to launch another app?==
+
<!--T:65-->
 +
The solutions:
  
 +
<!--T:66-->
 +
Let the app dlopen the part. This is what KOffice does. However this limits the app to the very limited ReadOnlyPart/ReadWritePart API. Keep in mind that you can't call a non-virtual method whose implementation you don't link to. The solution is to define a ReadWritePart-derived class (like we have in koffice: KoDocument), with new virtual methods. Either this derived class has code (and you need a lib shared by the app and the part, see point 2 below), or an abstract interface (header file only) is enough. You can also use known interfaces to child objects of the part instead of changing the base class of the part itself - this is the solution used by e.g. KParts::BrowserExtension.
 +
 +
<!--T:67-->
 +
Define a common library with the common classes and let both the part and the app use it. That library can be noinst_ or lib_, both work. In the first case the compiled object code is duplicated, in the second case a real versioned lib will be installed. The idea here is that the part itself is not available to the app, but instead the part is a very thin wrapper around the same classes as the app uses. Only KParts-specific stuff remains in the part.
 +
 +
==What is the best way to launch another app?== <!--T:68-->
 +
 +
<!--T:69-->
 
In KDE there are several ways to start other programs from within your application. Here is a short summary of your options with reasons why you should or should not use them.  
 
In KDE there are several ways to start other programs from within your application. Here is a short summary of your options with reasons why you should or should not use them.  
===fork + exec===
+
 
 +
===fork + exec=== <!--T:70-->
 +
 
 +
<!--T:71-->
 
You never want to use this unless you have a very good reason why it is impossible to use KProcess.  
 
You never want to use this unless you have a very good reason why it is impossible to use KProcess.  
===KProcess===
+
 
 +
===KProcess=== <!--T:72-->
 +
 
 +
<!--T:73-->
 
You want to use this if you need to start a new process which needs to be a child of your process, e.g. because you want to catch stdout/stderr or need to send it data via stdin. You should never use this to start other KDE applications unless your application is called kgdb :-)
 
You want to use this if you need to start a new process which needs to be a child of your process, e.g. because you want to catch stdout/stderr or need to send it data via stdin. You should never use this to start other KDE applications unless your application is called kgdb :-)
  
===startServiceByDesktopPath===
+
===startServiceByDesktopPath=== <!--T:74-->
 +
 
 +
<!--T:75-->
 
Preferred way to launch desktop (KDE/Gnome/X) applications or KDE services. The application/service must have a .desktop file. It will make use of KDEinit for increased startup performance and lower memory usage. These benefits only apply to applications available as KDEinit loadable module (KLM)  
 
Preferred way to launch desktop (KDE/Gnome/X) applications or KDE services. The application/service must have a .desktop file. It will make use of KDEinit for increased startup performance and lower memory usage. These benefits only apply to applications available as KDEinit loadable module (KLM)  
===KRun===
 
Generic way to open documents/applications/shell commands. Uses startServiceBy.... where applicable. Offers the additional benefit of startup-notification.<br/> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] can start any application, from the binary or the desktop file, it will determine the mimetype of a file before running the preferred handler for it, and it can also start shell commands. This makes KRun the recommended way to run another program in KDE.
 
  
=== KToolInvocation::invokeBrowser ===
+
===KRun=== <!--T:76-->
 +
 
 +
<!--T:77-->
 +
Generic way to open documents/applications/shell commands. Uses startServiceBy.... where applicable. Offers the additional benefit of startup-notification.<br /> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] can start any application, from the binary or the desktop file, it will determine the mimetype of a file before running the preferred handler for it, and it can also start shell commands. This makes KRun the recommended way to run another program in KDE.
 +
 
 +
=== KToolInvocation::invokeBrowser === <!--T:78-->
 +
 
 +
<!--T:79-->
 
[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation::invokeBrowser] launches a web browser. The difference with using the more generic KRun on the webpage URL is that KRun has to determine the mimetype of the URL first (which, for HTTP, involves starting a download to read the headers), so if you know that the URL is an HTML webpage, use invokeBrowser, it will be faster.
 
[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation::invokeBrowser] launches a web browser. The difference with using the more generic KRun on the webpage URL is that KRun has to determine the mimetype of the URL first (which, for HTTP, involves starting a download to read the headers), so if you know that the URL is an HTML webpage, use invokeBrowser, it will be faster.
  
 +
<!--T:80-->
 
More details: the problem with KRun for webpages is that it delays the appearance of the  browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.
 
More details: the problem with KRun for webpages is that it delays the appearance of the  browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.
  
==How do I create and submit a patch to KDE?==
+
==How do I create and submit a patch to KDE?== <!--T:81-->
  
 +
<!--T:82-->
 
You have spotted a bug and you want to write the code to fix it. Or you want to code a specific feature. Sending a patch is very appreciated by developers. A tutorial is available but here is a description of how you should proceed:  
 
You have spotted a bug and you want to write the code to fix it. Or you want to code a specific feature. Sending a patch is very appreciated by developers. A tutorial is available but here is a description of how you should proceed:  
Get the latest KDE using SVN to check that the code you want to write has not been added yet.
 
Check the bug database to see if your bug is not worked on.
 
Get in contact with the author. His/her name is in the about box or in the source header. If the project has a mailing-list, browse the archives to see if your bug/feature has not been the subject of any discussion. If you can't find any mailing lists or author, simply write to kde-devel.
 
Post a message explaining your intentions. It is important to inform the author(s) about what you are planning because somebody might already be working on your feature, or a better design could be proposed by the author, or he could give you some good advice.
 
Next step is to code your feature. It is usually a good idea to keep an original at hand and to work on a copy. This allow to check the behaviours of both versions of the code. Respect the author's indentation and naming scheme, code carefully, think about side-effects and test everything many times.
 
Using the latest KDE code, make a diff using either svn diff or a diff -uNp original-dir new-dir. Don't send reversed patch. The first argument of diff should be the old directory and the second the new directory.
 
Send a mail to the author/mailing-list with your patch as attachment (don't forget to attach it :-) ).
 
People usually have some remarks on your work and you must work further on your patch to improve it. It is common to see three or four submission before acceptation.
 
  
 +
<!--T:83-->
 +
* Get the latest KDE using SVN to check that the code you want to write has not been added yet.
 +
* Check the bug database to see if your bug is not worked on.
 +
 +
<!--T:84-->
 +
* Get in contact with the author. His/her name is in the about box or in the source header. If the project has a mailing-list, browse the archives to see if your bug/feature has not been the subject of any discussion. If you can't find any mailing lists or author, simply write to kde-devel.
 +
 +
<!--T:85-->
 +
* Post a message explaining your intentions. It is important to inform the author(s) about what you are planning because somebody might already be working on your feature, or a better design could be proposed by the author, or he could give you some good advice.
 +
 +
<!--T:86-->
 +
* Next step is to code your feature. It is usually a good idea to keep an original at hand and to work on a copy. This allow to check the behaviour of both versions of the code. Respect the author's indentation and naming scheme, code carefully, think about side-effects and test everything many times.
 +
 +
<!--T:87-->
 +
* Using the latest KDE code, make a diff using either svn diff or a diff -uNp original-dir new-dir. Don't send reversed patch. The first argument of diff should be the old directory and the second the new directory.
 +
 +
<!--T:88-->
 +
* Send a mail to the author/mailing-list with your patch as attachment (don't forget to attach it :-) ).
 +
 +
<!--T:89-->
 +
* People usually have some remarks on your work and you must work further on your patch to improve it. It is common to see three or four submission before acceptation.
 +
 +
<!--T:90-->
 
Ok, you have done it, your code has been included in KDE. You are now fully part of the KDE project. Thanx a lot.  
 
Ok, you have done it, your code has been included in KDE. You are now fully part of the KDE project. Thanx a lot.  
  
==How do I make my application Xinerama and multi-head safe?==
+
==How do I make my application Xinerama and multi-head safe?== <!--T:91-->
  
 +
<!--T:92-->
 
Never make assumptions about the geometry of the "desktop" or the arrangement of the screens. Make use of the following functions from kglobalsettings.h:  
 
Never make assumptions about the geometry of the "desktop" or the arrangement of the screens. Make use of the following functions from kglobalsettings.h:  
 
<syntaxhighlight lang="cpp-qt">
 
<syntaxhighlight lang="cpp-qt">
Line 188: Line 285:
 
Use splashScreenDesktopGeometry() to determine the geometry of the desktop when you want to display an application splash screen. Use desktopGeometry() to determine the geometry of the desktop with respect to a given point on the desktop, or with respect to a given widget. Do not use the Qt class QDesktopWidget to determine these values yourself. The KDE functions take the user's settings into account, something the Qt functions cannot do.  
 
Use splashScreenDesktopGeometry() to determine the geometry of the desktop when you want to display an application splash screen. Use desktopGeometry() to determine the geometry of the desktop with respect to a given point on the desktop, or with respect to a given widget. Do not use the Qt class QDesktopWidget to determine these values yourself. The KDE functions take the user's settings into account, something the Qt functions cannot do.  
  
 +
<!--T:93-->
 
It is ideal to try to avoid using the desktop geometry altogether. Your application will be much more standards compliant if you let the window manager place your windows for you. When this is not possible, you have the aforementioned functions available. Please beware that the geometry that is returned from these functions may not start at (0,0)! Do your math correctly!  
 
It is ideal to try to avoid using the desktop geometry altogether. Your application will be much more standards compliant if you let the window manager place your windows for you. When this is not possible, you have the aforementioned functions available. Please beware that the geometry that is returned from these functions may not start at (0,0)! Do your math correctly!  
  
 +
<!--T:94-->
 
One other caution: Both KWin and the NETWM specification have severe difficulties handling struts with Xinerama or "merged" displays. This can result in dead areas on the screen, for instance if kicker does not span a whole edge. There is not much that can be done about this, and you should try to avoid hacks to circumvent this at this time. We hope to find a proper solution for this soon.  
 
One other caution: Both KWin and the NETWM specification have severe difficulties handling struts with Xinerama or "merged" displays. This can result in dead areas on the screen, for instance if kicker does not span a whole edge. There is not much that can be done about this, and you should try to avoid hacks to circumvent this at this time. We hope to find a proper solution for this soon.  
  
==I get an error about KDE not finding UIC plugins, but I know they're installed. What's wrong?==
+
==I get an error about KDE not finding UIC plugins, but I know they're installed. What's wrong?== <!--T:95-->
  
 +
<!--T:96-->
 
This is almost certainly an installation problem, not a KDE code problem. A number of problems can lead to this, but most likely you have more than one version of Qt laying around and the configure script is calling a different one than KDE is using.  
 
This is almost certainly an installation problem, not a KDE code problem. A number of problems can lead to this, but most likely you have more than one version of Qt laying around and the configure script is calling a different one than KDE is using.  
  
 +
<!--T:97-->
 
Another thing that may help is to rebuild and reinstall your kdewidgets.so file, which is located in the kdelibs/kdewidgets directory. Note that if you *do* have multiple versions of Qt, this may compile against the wrong one.
 
Another thing that may help is to rebuild and reinstall your kdewidgets.so file, which is located in the kdelibs/kdewidgets directory. Note that if you *do* have multiple versions of Qt, this may compile against the wrong one.
 +
 +
<!--T:98-->
 
This problem creeps up on various mailing lists occasionally, so looking at the archives on lists.kde.org may be helpful.
 
This problem creeps up on various mailing lists occasionally, so looking at the archives on lists.kde.org may be helpful.
  
==I put some functions in anonymous namespace and someone reverted it and made those functions static, why?==
+
==I put some functions in anonymous namespace and someone reverted it and made those functions static, why?== <!--T:99-->
  
Symbols defined in a C++ anonymous namespace do NOT have internal linkage. Anonymous namespaces only give an unique name for that translation unit and that is it; they don't change the linkage of the symbol at all. Linkage isn't changed on those because the second phase of two-phase name lookup ignores functions with internal linkages. Also, entities with internal linkage cannot be used as template arguments.  
+
<!--T:100-->
 +
Symbols defined in a C++ anonymous namespace do NOT have internal linkage. Anonymous namespaces only give an unique name for that translation unit and that is it; they don't change the linkage of the symbol at all.  
  
==Can I delete a NULL pointer?==
+
<!--T:101-->
 +
Linkage isn't changed on those because the second phase of two-phase name lookup ignores functions with internal linkages. Also, entities with internal linkage cannot be used as template arguments.
  
Yes. Calling delete on a null pointer is a noop in C++. Having "if (ptr) delete ptr;" is redundant. Doing "ptr = 0;" after a delete is a good idea, especially if the delete can be called on it from a different code path.
+
==Can I delete a NULL pointer?== <!--T:102-->
[[Category:FAQs]]
+
  
==My locally installed application doesn't run, but KDEDIRS is set correctly, what's going on?==
+
<!--T:103-->
 +
Yes. Calling delete on a null pointer is a noop in C++. Having "if (ptr) delete ptr;" is redundant. Doing <code>ptr = 0;</code> after a delete is a good idea, especially if the delete can be called on it from a different code path.
  
 +
==My locally installed application doesn't run, but KDEDIRS is set correctly, what's going on?== <!--T:104-->
 +
 +
<!--T:105-->
 
If you're running a 64 bits system, your libraries might have been compiled with the -DLIB_SUFFIX=64 option given to cmake. If your application wasn't compiled with that option, it'll get its modules installed into $prefix/lib/kde4, not $prefix/lib64/kde4 -- and then it will not be found. Easy solutions: a symlink to lib64 or compile your code with -DLIB_SUFFIX=64, too.
 
If you're running a 64 bits system, your libraries might have been compiled with the -DLIB_SUFFIX=64 option given to cmake. If your application wasn't compiled with that option, it'll get its modules installed into $prefix/lib/kde4, not $prefix/lib64/kde4 -- and then it will not be found. Easy solutions: a symlink to lib64 or compile your code with -DLIB_SUFFIX=64, too.
 +
</translate>
 +
 +
[[Category:FAQs]]

Latest revision as of 13:41, 13 July 2012

Other languages:English 100% • ‎Japanese 34% • ‎Brazilian Portuguese 25%
noframe
 
This section needs improvements: Please help us to

cleanup confusing sections and fix sections which contain a todo


The build system has changed in KDE4.

Contents

[edit] How do I start a new application?

The easiest way is to use kdesdk/kapptemplate to generate the CMakeLists.txt. Or you can just copy a CMakeLists.txt from another app and install it in a new toplevel directory of existing KDE sources. Or you can start the old way, from scratch.

[edit] What is plasma, kpart, kio, kdeinit, ...

Check TechBase, especially the architecture documents. Check also the kde book.

[edit] Do I really need to use kpart?

Well, you are not forced to but it is a lot better. KPart allows powerful code reuse. Given how simple it is to use the technology and how widely it is deployed, it is a shame not to use it if you can.

[edit] How do I write a CMakeLists.txt?

Please follow this CMake tutorial.

[edit] What targets are available to make?

  • all: the default target (the one you get when typing "make").
  • clean: removes all the generated files
  • distclean: also removes the files generated by Makefile.cvs Not very useful within KDE (see dist for the "dist" concept and svn-clean for a better way to make really clean).
  • dist: supposedly for making a tarball out of SVN sources, but not very well supported within KDE. Better use kdesdk/scripts/cvs2pack for that.
  • force-reedit: re-run automake and am_edit on the Makefile.am
  • install: well, install everything :)
  • install-strip: install everything and strips binaries (removes debugging symbols).
  • install-exec: only install the binaries and libraries
  • install-data: only install the data files
  • check: compiles the test programs (i.e. those defined with check_PROGRAMS). It is even possible to actually run some tests during "make check", see kdelibs/arts/tests/Makefile.am

[edit] I have a checkout of SVN, there is no configure and no Makefile?

Use make -f Makefile.cvs It will run all the Makefile generation steps

[edit] How can I temporarily exclude certain directories from build?

While hacking a program it might be useful to exclude certain directories from build that would otherwise be recompiled, but don't actually need to be. Also, if you checked out source code that didn't compile and you don't have the time or knowledge to fix the error you might want to turn off compilation of the directory alltogether. There are two cases. Toplevel directories, and subdirectories. For toplevel directories you can simply erase them (or not check them out).

If for some reason you don't want to do that, you can also set DO_NOT_COMPILE="someapp" before calling configure, which will make configure skip "someapp". To only compile very few toplevel dirs, instead of using DO_NOT_COMPILE to exclude most of them, you can list in a file named inst-apps, at the toplevel, the toplevel subdirs you want to compile.

To turn off compilation of any directory, including subdirectories, you have to modify the Makefile or Makefile.am files. Makefile.am is not recommended because that file is in KDE Subversion and you could accidentally commit your changes. So we'll modify the Makefile instead here:

Open the Makefile in the directory immediately above the directory you want to exclude in a text editor and look for a variable SUBDIRS. It will often look somewhat like

SUBDIRS = share core ui . proxy taskmanager taskbar applets extensions data

Just remove the directory that you want to exclude and save your file. A new make will skip the directory you just removed.

Sometimes you'll have to look harder because the SUBDIRS variable consists of a number of other variables:

SUBDIRS = $(COMPILE_FIRST) $(TOPSUBDIRS) $(COMPILE_LAST)

Here you have to find the COMPILE_FIRST, TOPSUBDIRS and COMPILE_LAST variables. One of those contains the dir you want to exclude. Remove the directory where you find it and save the Makefile again. To undo your changes you can either regenerate the Makefile from scratch or revert to an older backup (you did make one, did you? :-). To regenerate a Makefile, just make force-reedit.

You can also copy the original line in the file when editing and make it a comment by prefixing a '#' in front of it. Then undoing the change is as easy as making the modified line a comment and removing the comment in the original line.

[edit] What are the various compilation options?

--enable-debug

Add debug symbols, disable optimisations and turns logging of kdDebug() on.

--disable-debug

The opposite of the previous one: enable optimisations and turns kdDebug() logging off.

--enable-final

Concatenates all .cpp files into one big .all_cpp.cpp file, and compiles it in one go, instead of compiling each .cpp file on its own. This makes the whole compilation much faster, and often leads to better optimised code, but it also requires much more memory. And it often results in compilation errors when headers included by different source files clash one with the other, or when using c static functions with the same name in different source files.

This is a good thing to do at packaging time, but of course not for developers, since a change in one file means recompiling everything.

--disable-fast-perl

By default KDE uses perl instead of sh and sed to convert Makefile.in into Makefile. This is an addition to autoconf done by Michael Matz. You can use this option to disable this but it is a lot slower.

[edit] Which compile option do you recommend?

If you are a developer, you should definitely compile Qt and KDE with --enable-debug. You will then be able to debug your program even inside Qt and KDE function calls. If you are just a user, you can still use --enable-debug. KDE will occupy more space on your hard disk but it won't slow down your desktop. The advantage is that you get stack trace when an application crashes. If you can reproduce a crashing behaviour, go to bugs.kde.org, check that your bug doesn't exist yet and submit it. It will help us improve kde. For Qt, the compilation options are explained in qt-copy/README.qt-copy.

[edit] Tips to increase compilation speed?

See --enable-final above :) . make final uses the all-in-one-file trick in the current directory even if --enable-final wasn't used, and make no-final does a normal compilation in the current directory even if --enable-final was used. Include your moc files! Header files declaring a QObject descendant have to be run through moc to produce a .moc file. This .moc file has to be compiled, for which two possibilities exists: compile it separately, or #include it in the C++ file implementing that above mentioned class. The latter is more efficient in term of compilation speed. BTW, kdesdk/scripts/includemocs does this automatically. Buy more ram, a faster machine and another processor. On a bi-PIII 866 MHz with 1GB of RAM, kde compiles at a decent speed :-)))

[edit] There is a STRIP variable set in the Makefile but it doesn't seem to be used?

The strip is done at install. To use it, use "make install-strip" instead of "make install".

[edit] What indentation should I use?

If you are working on an existing application, respect the author's indentation. Else, you can use whatever indentation you like.

[edit] What is the difference between i18n and I18N_NOOP?

If you do QString translatedStuff = i18n("foobar"); translatedStuff will contain the translation of "foobar", while for const char *markedStuff = I18N_NOOP("foobar"); markedStuff will still contain literal "foobar", but translators will know you want "foobar" translated so you can later on do QString translatedStuff = i18n(markedStuff); and get the translation of "foobar", which wouldn't work without that I18N_NOOP. So, normally you want to just use i18n(), but in cases where you absolutely need to pass something untranslated, but still need to translate it later or in the case that you have something to be translated before the KInstance exists, use I18N_NOOP().

[edit] I get "virtual tables error"?

This often comes from the moc files not being in sync with the sources, or not linked at all. Check that you are running the right moc. 'which moc' will tell it. Regenerate your moc files (make force-reedit; make clean; make).

[edit] I have added Q_OBJECT to myClassHeader.h but no moc files is generated?

You need am_edit to reparse your Makefile.am to generate the correct Makefile. If it's the first Q_OBJECT you're using in this directory, you'll need to re-run Makefile.cvs or create_makefile from kdesdk/scripts. Otherwise, you can simply run "make force-reedit".

[edit] To go quicker, I have coded my whole class in a cpp file, how do I get the moc files generated?

Hmm, don't do that, if some of the classes use the Q_OBJECT macro. Maybe METASOURCES=file.cpp might work for moc files though.

[edit] I have developed a kpart (or a plugin). I don't want to install it yet because it is not finished but I need that KDE finds it when I request it using KTrader or KLibLoader. How do I do that?

KDE searches its libraries in $KDEDIR/lib and in the lib directory of all the components of $KDEDIRS (note the additional 'S', this different from $KDEDIR). So, while you are still developing your library and don't want to install it, you can use this trick:

cd to your development directory, the one where your library is built.
Set up KDEDIRS so that it include your development directory: export KDEDIRS=`pwd`:$KDEDIR
Create a pseudo lib directory where KDE should find your component: ln -s .libs lib (all the objects and libraries are built in the .libs directory).
Run kbuildsycoca to inform KDE that it KDEDIRS has changed.

Now, KDE should find your library when using KTrader or KLibLoader.

[edit] How can I install additional KDE stuff when I am not root?

If want to install your application privately, configure it with another prefix: for $HOME/kdeprefix, use configure --prefix=$HOME/kdeprefix. Then let KDE know about this prefix: set KDEDIRS to $HOME/kdeprefix:$KDEDIR. To make KDE aware of new prefixes, one can also edit /etc/kderc and add

[Directories]
prefixes=/the/new/prefix

but this doesn't answer this specific question ;-) Make sure to run "kbuildsycoca" after setting the new KDEDIRS.

[edit] My kpart lib is not listed when I request it with KTrader

The mimetype database must be rebuilt when you install new services (such as applications or parts). In theory this happens by itself (kded is watching those directories), but in doubt, run "kbuildsycoca". The best way to debug trader-related problems is to use ktradertest: cd kdelibs/kio/tests; make ktradertest, then run ./ktradertest to see how to use it.

[edit] I changed something in kdelibs, installed the new lib, but new KDE apps don't seem to use it?

The solution is simple: start new apps from a command line, then they will use the new lib.

The reason is that applications started by other KDE applications (kicker, minicli, konqueror, etc.) are started via kdeinit, which loads the libs when KDE starts. So the "old" version of the libs keep being used. But if you want kdeinit to start using the new libs, simply restart it. This is done by typing kdeinit in a terminal.

This is necessary if you can't start things from the command line - e.g. for a kioslave. If you change something in kio, you need to restart kdeinit and kill the running kioslave, so that a new one is started.

[edit] I'm developing both a KPart and a standalone application, how do I avoid duplicated code?

Apps are often tempted to link to their part because they of course have much functionality in common. However this is wrong for the reasons below.

A lib is something you link to, a module is something you dlopen. You can't dlopen a lib ; you can't link to a module.

A lib has a version number and is installed in $libdir (e.g. $KDEDIR/lib) a module doesn't have a version number (in its name), it's more like a binary (we don't have konqueror-1.14.23 either :), and is installed into kde_moduledir (e.g. $KDEDIR/lib/kde3) (which means it's not in the search path for ld.so, so this breaks on systems without -rpath).

If you didn't understand the above, don't worry. The point is: you should NOT make your application link to your (or any other) KPart, nor any other kind of dlopened module.

The solutions:

Let the app dlopen the part. This is what KOffice does. However this limits the app to the very limited ReadOnlyPart/ReadWritePart API. Keep in mind that you can't call a non-virtual method whose implementation you don't link to. The solution is to define a ReadWritePart-derived class (like we have in koffice: KoDocument), with new virtual methods. Either this derived class has code (and you need a lib shared by the app and the part, see point 2 below), or an abstract interface (header file only) is enough. You can also use known interfaces to child objects of the part instead of changing the base class of the part itself - this is the solution used by e.g. KParts::BrowserExtension.

Define a common library with the common classes and let both the part and the app use it. That library can be noinst_ or lib_, both work. In the first case the compiled object code is duplicated, in the second case a real versioned lib will be installed. The idea here is that the part itself is not available to the app, but instead the part is a very thin wrapper around the same classes as the app uses. Only KParts-specific stuff remains in the part.

[edit] What is the best way to launch another app?

In KDE there are several ways to start other programs from within your application. Here is a short summary of your options with reasons why you should or should not use them.

[edit] fork + exec

You never want to use this unless you have a very good reason why it is impossible to use KProcess.

[edit] KProcess

You want to use this if you need to start a new process which needs to be a child of your process, e.g. because you want to catch stdout/stderr or need to send it data via stdin. You should never use this to start other KDE applications unless your application is called kgdb :-)

[edit] startServiceByDesktopPath

Preferred way to launch desktop (KDE/Gnome/X) applications or KDE services. The application/service must have a .desktop file. It will make use of KDEinit for increased startup performance and lower memory usage. These benefits only apply to applications available as KDEinit loadable module (KLM)

[edit] KRun

Generic way to open documents/applications/shell commands. Uses startServiceBy.... where applicable. Offers the additional benefit of startup-notification.
KRun can start any application, from the binary or the desktop file, it will determine the mimetype of a file before running the preferred handler for it, and it can also start shell commands. This makes KRun the recommended way to run another program in KDE.

[edit] KToolInvocation::invokeBrowser

KToolInvocation::invokeBrowser launches a web browser. The difference with using the more generic KRun on the webpage URL is that KRun has to determine the mimetype of the URL first (which, for HTTP, involves starting a download to read the headers), so if you know that the URL is an HTML webpage, use invokeBrowser, it will be faster.

More details: the problem with KRun for webpages is that it delays the appearance of the browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.

[edit] How do I create and submit a patch to KDE?

You have spotted a bug and you want to write the code to fix it. Or you want to code a specific feature. Sending a patch is very appreciated by developers. A tutorial is available but here is a description of how you should proceed:

  • Get the latest KDE using SVN to check that the code you want to write has not been added yet.
  • Check the bug database to see if your bug is not worked on.
  • Get in contact with the author. His/her name is in the about box or in the source header. If the project has a mailing-list, browse the archives to see if your bug/feature has not been the subject of any discussion. If you can't find any mailing lists or author, simply write to kde-devel.
  • Post a message explaining your intentions. It is important to inform the author(s) about what you are planning because somebody might already be working on your feature, or a better design could be proposed by the author, or he could give you some good advice.
  • Next step is to code your feature. It is usually a good idea to keep an original at hand and to work on a copy. This allow to check the behaviour of both versions of the code. Respect the author's indentation and naming scheme, code carefully, think about side-effects and test everything many times.
  • Using the latest KDE code, make a diff using either svn diff or a diff -uNp original-dir new-dir. Don't send reversed patch. The first argument of diff should be the old directory and the second the new directory.
  • Send a mail to the author/mailing-list with your patch as attachment (don't forget to attach it :-) ).
  • People usually have some remarks on your work and you must work further on your patch to improve it. It is common to see three or four submission before acceptation.

Ok, you have done it, your code has been included in KDE. You are now fully part of the KDE project. Thanx a lot.

[edit] How do I make my application Xinerama and multi-head safe?

Never make assumptions about the geometry of the "desktop" or the arrangement of the screens. Make use of the following functions from kglobalsettings.h:

 static QRect KGlobalSettings::splashScreenDesktopGeometry(); 
 static QRect KGlobalSettings::desktopGeometry(const QPoint& point); 
 static QRect KGlobalSettings::desktopGeometry(QWidget *w);

Use splashScreenDesktopGeometry() to determine the geometry of the desktop when you want to display an application splash screen. Use desktopGeometry() to determine the geometry of the desktop with respect to a given point on the desktop, or with respect to a given widget. Do not use the Qt class QDesktopWidget to determine these values yourself. The KDE functions take the user's settings into account, something the Qt functions cannot do.

It is ideal to try to avoid using the desktop geometry altogether. Your application will be much more standards compliant if you let the window manager place your windows for you. When this is not possible, you have the aforementioned functions available. Please beware that the geometry that is returned from these functions may not start at (0,0)! Do your math correctly!

One other caution: Both KWin and the NETWM specification have severe difficulties handling struts with Xinerama or "merged" displays. This can result in dead areas on the screen, for instance if kicker does not span a whole edge. There is not much that can be done about this, and you should try to avoid hacks to circumvent this at this time. We hope to find a proper solution for this soon.

[edit] I get an error about KDE not finding UIC plugins, but I know they're installed. What's wrong?

This is almost certainly an installation problem, not a KDE code problem. A number of problems can lead to this, but most likely you have more than one version of Qt laying around and the configure script is calling a different one than KDE is using.

Another thing that may help is to rebuild and reinstall your kdewidgets.so file, which is located in the kdelibs/kdewidgets directory. Note that if you *do* have multiple versions of Qt, this may compile against the wrong one.

This problem creeps up on various mailing lists occasionally, so looking at the archives on lists.kde.org may be helpful.

[edit] I put some functions in anonymous namespace and someone reverted it and made those functions static, why?

Symbols defined in a C++ anonymous namespace do NOT have internal linkage. Anonymous namespaces only give an unique name for that translation unit and that is it; they don't change the linkage of the symbol at all.

Linkage isn't changed on those because the second phase of two-phase name lookup ignores functions with internal linkages. Also, entities with internal linkage cannot be used as template arguments.

[edit] Can I delete a NULL pointer?

Yes. Calling delete on a null pointer is a noop in C++. Having "if (ptr) delete ptr;" is redundant. Doing ptr = 0; after a delete is a good idea, especially if the delete can be called on it from a different code path.

[edit] My locally installed application doesn't run, but KDEDIRS is set correctly, what's going on?

If you're running a 64 bits system, your libraries might have been compiled with the -DLIB_SUFFIX=64 option given to cmake. If your application wasn't compiled with that option, it'll get its modules installed into $prefix/lib/kde4, not $prefix/lib64/kde4 -- and then it will not be found. Easy solutions: a symlink to lib64 or compile your code with -DLIB_SUFFIX=64, too.


This page was last modified on 13 July 2012, at 13:41. This page has been accessed 17,285 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal