Difference between revisions of "Getting Started/Using an IDE with KDE4"

Jump to: navigation, search
m (Text replace - "</code>" to "</syntaxhighlight>")
(KDevelop 4)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=== KDevelop 3 (outdated by KDevelop 4) ===
+
== Eclipse ==
 
+
This section will explain how to use KDevelop 3.4 to develop KDE 4 applications. If you have any questions, corrections or rants about this section, please post them on the discussion page.
+
 
+
==== Prerequisites ====
+
 
+
You need at least KDevelop 3.4 for this, which is still a KDE 3 application. Versions lower than 3.4 do not have Qt 4 support among other things. You can get KDevelop at the [http://www.kdevelop.org/index.html?filename=3.4/download.html KDevelop homepage]. Make sure you install KDevelop like all other KDE 3 applications, '''not''' with your ''kde-devel'' user.
+
 
+
You also need the lastest ''GDB'' version, which is currently 6.6.0.
+
Note that the GDB version which is shipped with '''openSuse 10.3 is broken''', it constantly crashes when examining variables (which KDevelop does automatically). Use the GDB version from [http://download.opensuse.org/repositories/home:/amilcarlucas/openSUSE_10.3/ this repository] instead.
+
 
+
You need to have the kdelibs API documentation locally, which is described in the [[Development/Tools/apidox|build instructions]].
+
 
+
You also need ''ctags'', ''htdig'', ''htmerge'' and ''htsearch''. ''valgrind'' and ''callgrind'' can also be useful.
+
 
+
Be sure you followed the steps in the KDE 4 [[Getting_Started/Build|build instructions]] and have a working KDE 4 environment.  Make sure simple KDE 4 applications like ''Konsole'' or ''KWrite'' can be started from the command line of the ''kde-devel'' user without problems.
+
 
+
The following steps are all done with the ''kde-devel'' user. You need to login as that user by typing
+
su - kde-devel
+
 
+
KDevelop has no native support for CMake projects. Fortunately, CMake has the ability to generate KDevelop project files itself. In order to do this, you need to pass the ''-GKDevelop3'' flag to the ''cmake'' command. This tells CMake to generate project files for KDevelop alongside the normal makefiles. The best way to do this is to modify your ''cmakekde'' function in your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|{{path|.bashrc}}]]. Just change
+
<syntaxhighlight lang="bash">
+
cmake $srcFolder -DCMAKE_INSTALL_PREFIX=$KDEDIR \
+
-DCMAKE_BUILD_TYPE=debugfull&& \
+
make && \
+
make install;
+
</syntaxhighlight>
+
to
+
<syntaxhighlight lang="bash">
+
cmake $srcFolder -GKDevelop3 -DCMAKE_INSTALL_PREFIX=$KDEDIR \
+
-DCMAKE_BUILD_TYPE=debugfull&& \
+
make && \
+
make install;
+
</syntaxhighlight>
+
 
+
After you have done that, re-login so that the changes to the {{path|.bashrc}} file take effect. Then you need to rerun ''cmakekde'' in the (root) build directory of the project you want to work on with KDevelop (if you didn't use ''-GKDevelop3'' on the [[Getting_Started/Build/Environment|building step]]). For example, if you want to work on Konsole, which lives in ''kdebase'', you need to run cmakekde in the {{path|$KDE_BUILD/KDE/kdebase}} directory. This unfortunately completely rebuilds everything, but only once when you change the generator.
+
 
+
Since all environment variables of the kde-devel user are KDE 4 specific, these need to be set back to match your KDE 3 environment before starting KDevelop.
+
A simple way to do this is to add the following function to your {{path|.bashrc}}:
+
 
+
<syntaxhighlight lang="bash">
+
function start3app {
+
  mkdir -p /tmp/$USER-kde
+
  export PATH=/opt/kde3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
+
  export LD_LIBRARY_PATH=
+
  export KDETMP=/tmp/$USER-kde
+
  export KDEVARTMP=/var/tmp/$USER-kde
+
  export KDEHOME=$HOME/.kde
+
  export KDEDIR=/usr
+
  export KDEDIRS=$KDEDIR
+
  export DISPLAY=:0
+
  eval "$@"
+
  source $HOME/.bashrc  #Reset environment variables again
+
}
+
</syntaxhighlight>
+
 
+
The ''PATH'' and ''LD_LIBRARY_PATH'' variables are taken from the KDE 3 user, and they may be different on your system. Type <syntaxhighlight lang="bash">echo $PATH</syntaxhighlight> and <syntaxhighlight lang="bash">echo $LD_LIBRARY_PATH</syntaxhighlight> as normal KDE 3 user to get these values. The above function assumes that KDE 3 is installed in the {{path|/usr}} prefix, as it is the case on Debian-based systems. If your KDE 3 is installed to a different prefix, you need to change the line setting ''KDEDIR'' accordingly. Here's an example how you find out your KDE installation prefix; in this example it is /opt/kde3:
+
 
+
<syntaxhighlight lang="bash">
+
kde-config --prefix
+
/opt/kde3
+
</syntaxhighlight>
+
 
+
Now you should be able to start KDevelop by typing <tt>start3app kdevelop</tt>. Do that now.
+
 
+
{{tip|
+
You can start any KDE 3 application with the <tt>start3app</tt> function. Useful candidates include ''Kompare'' and ''kdesvn''.
+
 
+
However, you can not start ''KDbg'' this way to debug KDE 4 applications, since then the environment variables for the debugged application are wrong.
+
}}
+
<!--
+
{{tip|
+
Instead of starting KDevelop by using the ''start3app'' script as ''kde-devel'' user, you can also use the KDE run dialog ''(Alt+F2)'' to start KDevelop:
+
 
+
[[Image:Minicli.png]]
+
 
+
This starts KDevelop as ''kde-devel'' user but uses the environment variables of the normal user, just like the ''start3app'' script does.
+
}}
+
-->
+
 
+
===== TroubleShooting =====
+
 
+
'''Symptome:''' kdevelop says "cannot talk to klauncher". You cannot open a file.
+
 
+
'''Solution:''' add your KDE library path to LD_LIBRARY_PATH, e.g.:
+
export LD_LIBRARY_PATH=/opt/kde3/lib
+
 
+
==== Setting up KDevelop ====
+
 
+
Now that KDevelop has started, you need to adjust a few settings. Go to ''Settings->Configure KDevelop...->Documentation'' for this. Remove all entries that are not relevant to KDE 4 coding.
+
 
+
{{note|Although environment variables like $HOME are used in this section, you should replace them with real paths because KDevelop does not resolve environment variables.}}
+
 
+
Optionally, you can add the kdelibs API documentation. You must [[Development/Tools/apidox|create it beforehand]]. Then add the documentation by clicking ''Add...''. In this dialog, use the following settings:
+
* ''Type'': Doxygen Documentation Collection (needs to be set first)
+
* ''Location'': {{path|$KDE_SRC/KDE/kdelibs/kdelibs-apidocs/index.html}}
+
 
+
Now add the Qt API documentation, which also must be [[Development/Tools/apidox|created beforehand]], using the following settings:
+
* ''Type'': Qt Documentation Collection (needs to be set first)
+
* ''Location'': {{path|$HOME/qt-copy/doc/html/qt.dcf}}
+
 
+
After you have added kdelibs and Qt API documentation, make sure all checkboxes (''TOC'',''Index'' and ''Search'') are enabled. Then, go to the ''Full Text Search'' tab and make sure the paths to the ''htdig'', ''htmerge'' and ''htsearch'' executables are correct. You can then close the settings dialog.
+
 
+
Now it is time to open the project you want to work on by clicking ''Project->Open Project...''. The project files are located in the build directory. For example, if you want to work on Konsole, you need to open {{path|$KDE_BUILD/KDE/kdebase/apps/konsole/konsole.kdevelop}}. You now need to adjust a few project-specific settings in ''Project->Project Options''. You need to do this every time you start to work on a different project.
+
 
+
{{note|
+
Sometimes, a KDevelop project file is not present for the folder you want to work on.
+
 
+
This can have several reasons, it depends on how the CMake files are written. Usually, CMake files which have a <tt>project(projectname)</tt> statement in them should work fine. Once you are familiar enough with CMake, you can try adding the statement.
+
 
+
A workaround for this is to simply use the KDevelop project file of the parent folder, or even higher. In this case, you need to use the <tt>Make Active Directory</tt> entry in the context menu of the <tt>File Selector</tt> sidetab. With this, you can ignore the other unwanted folders when building and installing.
+
}}
+
 
+
* ''C++ Support->Code Completion''
+
:Here you need to add code completion databases for Qt and kdelibs, and more if you like, for example you might need a database for ''kdepimlibs'' when working on ''kdepim''.
+
 
+
:For kdelibs, click the ''Add...'' button and choose ''KDevelop Custom Directory PCS Importer'', then add your KDE include directory ({{path|$HOME/kde/include}}) to the list and proceed. You can use the file selection dialog and the ''Add'' button to add it.
+
 
+
:Now, add the database for Qt 4 by selecting ''KDevelop Qt4 PCS Importer'' this time. You need to select the Qt 4 include directory, which is {{path|$HOME/qt-copy/include}}.
+
 
+
{{note|The Qt4 PCS Importer is only needed if you didn't install Qt4, i.e. you use it directly from the build directory. The drawback of using the Qt4 importer is that it doesn't show progress and the application seems to hang while it imports. The alternative is to use the Custom Directory PCS Importer for this too}}
+
 
+
* ''C++ Support->Qt Options''
+
:Check ''Enable Qt options'' and choose Qt4 as your version. Set the ''QMake Binary'' path to {{path|$HOME/qt-copy/bin/qmake}}. Then choose ''Qt 4 style'' as ''Qt include syntax''. Use {{path|$HOME/qt-copy/bin/designer}} as ''Designer Binary''. Make sure to use the ''Change Plugin Paths'' dialog to add the plugin directory from KDE so you see the KDE widgets when designer is started. To do this add {{path|$HOME/kde/lib/kde4/plugins}} to the lineedit and then click the ''Add'' button.
+
 
+
* ''Run Options''
+
:Make sure you use the correct binary as ''Executable''. For example, if you want to run Konsole, this is {{path|$KDE_BUILD/KDE/kdebase/apps/konsole/src/konsole}}. You should add ''--nofork'' to the ''Debug Arguments'' or debugging some applications like ''KMail'' will not work at all.
+
 
+
:Because the ''start3app'' functions changes some environment variables, you need to change them back here so the KDE 4 applications can be run without problems from within KDevelop.
+
:For some applications, like Konsole, this is not strictly necessary, but others like KMail will crash if you do not change this.
+
:Simply click the ''Add / Copy'' button to add new environment variables. You will need the following, which are the same as in your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|{{path|.bashrc}}]]:
+
 
+
:{| border="1"
+
|-
+
! Name
+
! Value
+
|-
+
| KDEHOME
+
| $HOME/.kde4
+
|-
+
| PATH
+
| $KDEDIR/bin:$QTDIR/bin:/usr/local/bin:$PATH
+
|-
+
| LD_LIBRARY_PATH
+
| $KDEDIR/lib:$QTDIR/lib:$LD_LIBRARY_PATH
+
|-
+
| KDETMP
+
| /tmp/$USER-kde4
+
|-
+
| KDEVARTMP
+
| /var/tmp/$USER-kde4
+
|-
+
| KDEDIR
+
| $HOME/kde
+
|-
+
| KDEDIRS
+
| $KDEDIR
+
|-
+
| LD_BIND_NOW
+
| 42
+
|}
+
 
+
 
+
 
+
* ''Build Options->Build''
+
:Make sure the correct build directory is selected. Again, for Konsole, this would be {{path|$KDE_BUILD/KDE/kdebase/apps/konsole}}.
+
 
+
* ''Build Options->Make''
+
:You might want to check ''Abort on first error''. You also might want to add ''VERBOSE='' or ''VERBOSE=1'' to ''Additional make options'' to control the level of verbosity for the build process.
+
 
+
:If you have more than one processor or if you have access to an icecream cluster, you might want to check the ''Run multiple jobs'' option and set the ''Number of simultaneous jobs'' to the number of available processors. This increases the compile speed. It is the same as the <tt>-j</tt> option for ''make''.
+
 
+
* ''Formatting''
+
:You should set all options here to match the coding style of the project you are working on.
+
 
+
* ''CTags->General''
+
:You need to correctly set the ''Path to ctags binary'', which is {{path|/usr/bin/ctags}} on Debian-based systems.
+
 
+
:You probably want to enable the <tt>When more than one hit, go directly to the first</tt> option.
+
 
+
Now you have finished adjusting your project-specific settings. Now you should remove some plugins you do not need, in ''Settings->Configure Plugins...''. I for example disable the following plugins:
+
 
+
<small>Abbreviation Expansion, Code Snippets, Doxygen Support, Embedded Konsole, File Tree, '''Final Packaging Support''', "Open with" Menu Addon, QuickOpen, Regular Expression Tester, Scripting, '''Security Checker''', Shell Filtering and Insertion, Text Structure and Tools Menu Addition.</small>
+
 
+
You should at least disable the bold ones.
+
 
+
Now, open any source file if none is open already. This will enable the ''Settings->Configure Editor...'' entry, where you need to set the tab options to match the tab style used by the project you are working on. The important settings are:
+
* ''Appearance->Borders->Show line numbers'': Should be checked.
+
* ''Appearance->Borders->Show icon border'': Should be checked.
+
* ''Editing->Tabulators''
+
* ''Editing->Static Word Wrap->Show marker'': Should be checked
+
* ''Indentation->Automatic Indentation->Indentation mode'': Should be ''C Style''
+
* ''Indentation'' in general
+
 
+
In the mainwindow, click the ''CTags'' tab on the bottom tabbar, then click the ''Regenerate'' button to create a CTags database for easier source code navigation.
+
 
+
Now you have completed all essential configuration, congratulations!
+
 
+
==== Using KDevelop ====
+
 
+
Refer to the [http://docs.kde.org/development/en/kdevelop/kdevelop/ KDevelop manual] for general help using KDevelop. The following section will only deal with special cases for KDE 4.
+
 
+
===== Debugging =====
+
 
+
KDE apps have many symbols, which means that you need a lot of memory to get a decent loading times for debugging. To quote a GDB developer: "I would be reluctant to debug KDE on something with <1GB RAM."
+
If the stepping function of the debugger is slow for you, try the following tips:
+
* Hide local variables. The <tt>Locals</tt> part of the variable tab on the left causes a big slowdown when stepping if you have many local variables. Simple collapse the <tt>Locals</tt> part of the tree, the local variables are then not updated every step. You can still examine variables by using the <tt>Evaluate expression</tt> function.
+
* Use the patch at http://bugs.kde.org/show_bug.cgi?id=143977. It prevents the update of the framestack widget at each step, speeding up stepping considerably. The patch introduces some minor glitches, which is why it is not yet commited.
+
 
+
{{Note|
+
KDevelop does not yet support modifing the CMake build system. This means you can not use KDevelop to add or remove files from the project or to change any other aspect of your project's build process.
+
 
+
You need to modify the CMake files by hand and then rerun <tt>cmakekde</tt> instead. Read the [[Development/Tutorials/CMake|CMake tutorial]] to learn how to do this.
+
}}
+
 
+
{{tip|When you work on libraries, you first need to install them before you can test or debug your changes.
+
Since this is cumbersome and time consuming, you should create symlinks ''(ln -s)'' pointing from the build directory to the installation directory for all affected libraries.
+
 
+
Often, even simple programs use libraries internally, for example the settings dialog of Konsole is really a library.}}
+
 
+
=== Eclipse ===
+
  
 
     {|align="right"  
 
     {|align="right"  
 
     |[[image:Snapshot-eclipse.png|right|thumb|200px|KDE4's ktimetracker loaded as eclipse project]]
 
     |[[image:Snapshot-eclipse.png|right|thumb|200px|KDE4's ktimetracker loaded as eclipse project]]
 
     |}
 
     |}
This describes how to use Eclipse to develop KDE 4 applications. It has been tested with Eclipse Ganymed and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use [http://userbase.kde.org/ktimetracker ktimetracker] from the kdepim module, other applications short work analog.
+
This describes how to use Eclipse to develop KDE 4 applications. It has been tested with Eclipse Ganymede and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use [http://userbase.kde.org/KTimeTracker KTimeTracker] from the kdepim module, other applications should work likewise.
  
 
Using this description you will be able to
 
Using this description you will be able to
* update your working copy of KDE source code using the command svn
+
* update your working copy of KDE source code using the ''svn'' command
* build your KDE module using cmake
+
* build your KDE module using CMake
* build your KDE application from within eclipse using make
+
* build your KDE application from within Eclipse using Make
* compile and run your application with one click from eclipse
+
* compile and run your application with one click from Eclipse
 
* get auto-completion when editing KDE source code
 
* get auto-completion when editing KDE source code
* have an overview and navigation about your classes within eclipse
+
* have an overview and navigation about your classes within Eclipse
 
* have call trees for your functions
 
* have call trees for your functions
  
==== Set up Eclipse with KDE  ====
+
=== Set up Eclipse with KDE  ===
  
 
* Check your requirements
 
* Check your requirements
: Trying with a virtual machine [[User:Tstaerk|I]] had problems starting Eclipse with less than 1 GB RAM. After assigning 3 GB RAM to my virtual machine, Eclipse finally started.  
+
: Trying with a virtual machine [[User:Tstaerk|I]] had problems starting Eclipse with less than 1 GB RAM. After assigning 3 GB RAM to the virtual machine, Eclipse finally started.  
  
* Install eclipse
+
* Install Eclipse
  
: Download Eclipse IDE for C/C++ developers from http://www.eclipse.org. We unpack it to /home/user/eclipse.  
+
: Download Eclipse IDE for C/C++ developers from http://www.eclipse.org. Unpack it to /home/user/eclipse.  
  
 
* Install the CDT
 
* Install the CDT
  
: Download the Eclipse IDE for C/C++ Developers (68 MB) from http://www.eclipse.org/cdt/ and unpack it into your eclipse folder, in our case /home/user/eclipse.  
+
: Download the Eclipse IDE for C/C++ Developers (68 MB) from http://www.eclipse.org/cdt/ and unpack it into your Eclipse folder, in our case /home/user/eclipse.  
  
 
* Download kdepim
 
* Download kdepim
  
: As said, we use kdepim as example here. So, download ("checkout") kdepim using svn, e.g. as anonymous:  
+
: As said, we use kdepim as example here. So, download ("checkout") kdepim using git (for advanced git-usage see [[Development/Git/Configuration]], especially [[Development/Git/Configuration#URL_Renaming|URL-Renaming]]):
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepim
+
<syntaxhighlight lang="bash">
: We assume you checked out into /home/user/kdepim.  
+
cd /home/user
 +
git clone git://anongit.kde.org/kdepim
 +
</syntaxhighlight>
 +
: This will check out into /home/user/kdepim. (Our sample setup for this tutorial)
  
 
* Compile kdepim
 
* Compile kdepim
  
: Compile kdepim so the usual makefiles are present for all kdepim applications. If you have problems doing this, follow our [[Getting Started/Build|build instructions]]  
+
: Compile kdepim so the usual makefiles are present for all kdepim applications. If you have problems doing this, follow our [[Getting Started/Build|build instructions]].
  
* Import your project into eclipse
+
* Import your project into Eclipse
  
: Surprise: To import your project, you should not use "File -&gt; Import". Rather do: File -> New -> C++ Project -> Makefile project -> Empty Project -> un-tag "use default location" -> choose /home/user/kdepim/ktimetracker. Call it "ktimetracker".
+
: Surprise: To import your project, you cannot use "File -> Import". Rather do: File -> New -> C++ Project -> Makefile project -> Empty Project -> un-tag "use default location" -> choose /home/user/kdepim/ktimetracker. Call it "ktimetracker".
  
 
* Build your project
 
* Build your project
Line 269: Line 52:
 
: Choose Project -> Properties -> Run/Debug Settings -> New. As project, enter ''ktimetracker'', as C/C++ Application, enter /home/user/kdepim/ktimetracker/ktimetracker. Choose Apply -> Ok -> Ok. Now you can click on the "Run" button and start it.
 
: Choose Project -> Properties -> Run/Debug Settings -> New. As project, enter ''ktimetracker'', as C/C++ Application, enter /home/user/kdepim/ktimetracker/ktimetracker. Choose Apply -> Ok -> Ok. Now you can click on the "Run" button and start it.
  
==== Know-How ====
+
=== Know-How ===
  
===== Custom builders =====
+
==== Custom builders ====
  
If you want to integrate the cmake build step into your build toolchain, you will need to  
+
If you want to integrate the CMake build step into your build toolchain, you will need to  
 
* create a custom ''builder'' like this:
 
* create a custom ''builder'' like this:
cat >/bin/eclipsebuild<<EOF
+
<syntaxhighlight lang="bash">
cmake . && make -j4 && make install
+
echo "cmake . && make -j4 && make install" >/bin/eclipsebuild
EOF
+
chmod 777 /bin/eclipsebuild
chmod 777 /bin/eclipsebuild
+
</syntaxhighlight>
 
+
 
* Add your builder
 
* Add your builder
 
: Choose Project -> Properties -> Builders. Un-tag all existing builders. Click "new" -> Program -> (name it "Builder for KDE"). -> Location: /bin/eclipsebuild -> Working directory /home/user/workspace/myproject1/kdepim.
 
: Choose Project -> Properties -> Builders. Un-tag all existing builders. Click "new" -> Program -> (name it "Builder for KDE"). -> Location: /bin/eclipsebuild -> Working directory /home/user/workspace/myproject1/kdepim.
  
 
* Build
 
* Build
: Now you can build your project. Every time after you restarted eclipse, choose myproject1 -> Project -> Properties -> C/C++ Build -> Ok -> Project -> Build.
+
: Now you can build your project. Every time you restart eclipse, choose myproject1 -> Project -> Properties -> C/C++ Build -> Ok -> Project -> Build.
  
===== Revert what eclipse did =====
+
==== Revert what eclipse did ====
  
 
To revert what eclipse did to your project simply run
 
To revert what eclipse did to your project simply run
rm -rf .externalToolBuilders/ .project .cproject
+
<syntaxhighlight lang="bash">
 +
rm -rf .externalToolBuilders/ .project .cproject
 +
</syntaxhighlight>
  
===== Why Subversion does not work =====
+
==== Why Subversion does not work ====
  
When using eclipse's svn plugin and building a KDE program, you will get error messages complaining that your svn binary is too old. If you want to try and change this, here's how you get to that error:
+
When using Eclipse's svn plugin and building a KDE program, you will get error messages complaining that your svn binary is too old. If you want to try and change this, here is how you get to that error:
  
* Install the subversion plug-ins
+
* Install the Subversion plug-ins
 
: Help -> Software Updates -> Available Software -> Add Site -> http://download.eclipse.org/technology/subversive/0.7/update-site/ -> Add Site -> http://www.polarion.org/projects/subversive/download/eclipse/2.0/update-site/
 
: Help -> Software Updates -> Available Software -> Add Site -> http://download.eclipse.org/technology/subversive/0.7/update-site/ -> Add Site -> http://www.polarion.org/projects/subversive/download/eclipse/2.0/update-site/
  
Line 304: Line 88:
 
* Click on Install
 
* Click on Install
  
* Restart eclipse
+
* Restart Eclipse
  
 
* Import your KDE module
 
* Import your KDE module
Line 312: Line 96:
 
: Choose Project -> Properties -> C/C++ Build -> Builder Settings. Un-tag "use default build command", set "cmake" instead. Choose Project -> Properties -> C/C++ Build -> Behavior. Replace "all" by ".".
 
: Choose Project -> Properties -> C/C++ Build -> Builder Settings. Un-tag "use default build command", set "cmake" instead. Choose Project -> Properties -> C/C++ Build -> Behavior. Replace "all" by ".".
  
==== See also ====
+
=== See also ===
  
 
* http://javathreads.de/2008/07/subversion-unter-eclipse-ganymede-konfigurieren/
 
* http://javathreads.de/2008/07/subversion-unter-eclipse-ganymede-konfigurieren/
* http://nienhueser.de/blog/?p=19  
+
* http://nienhueser.de/blog/?p=19
  
=== QtCreator ===
+
== QtCreator ==
This describes how to use QtCreator to develop KDE 4 applications. It has been tested with QtCreator 1.2.80 and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use [http://userbase.kde.org/ktimetracker ktimetracker] from the kdepim module, other applications should work same or similar.
+
{|align="right"
 +
|[[image:Snapshot-qtcreator.png|right|thumb|200px|KDE4's ktimetracker loaded as QtCreator project]]
 +
|}
  
==== Load an existing project ====
+
Main article: [[Development/Tutorials/Using_Qt_Creator]]
 +
 
 +
This describes how to use QtCreator to develop KDE 4 applications. It has been tested with QtCreator 1.2.80 and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use [http://userbase.kde.org/ktimetracker ktimetracker] from the kdepim module, other applications should work likewise.
 +
 
 +
=== Load an existing project ===
 
As discussed here we use ktimetracker as example project.
 
As discussed here we use ktimetracker as example project.
 
* Import the CMakeLists.txt file
 
* Import the CMakeLists.txt file
 
File -> Open -> kdepim/CMakeLists.txt.
 
File -> Open -> kdepim/CMakeLists.txt.
* Configure qtcreator to build only ktimetracker
+
* Configure QtCreator to build only ktimetracker
 
Projects -> ktimetracker -> build settings -> Add a configuration ktimetracker.
 
Projects -> ktimetracker -> build settings -> Add a configuration ktimetracker.
  
As build directory choose kdepim. As arguments for cmake use e.g.
+
As build directory choose kdepim. As arguments for CMake use e.g.
. -DCMAKE_INSTALL_PREFIX=/usr/local -DLIB_SUFFIX=64 -DCMAKE_BUILD_TYPE=debugfull
+
<syntaxhighlight lang="cmake">
 +
. -DCMAKE_INSTALL_PREFIX=/usr/local -DLIB_SUFFIX=64 -DCMAKE_BUILD_TYPE=debugfull
 +
</syntaxhighlight>
  
==== Start a KDE project ====  
+
=== Start a KDE project ===  
To start a new project you need to tell qtcreator to use the KDE libraries when building. So, choose File -> New... and create your project. We will call it ''yourproject'' here. To be able to use KDE's libraries, go to your home directory, cd into ''yourproject'' and modify ''yourproject.pro''. Add a line
+
To start a new project you need to tell QtCreator to use the KDE libraries when building. So, choose File -> New... and create your project. We will call it ''yourproject'' here. To be able to use KDE's libraries, go to your home directory, change into ''yourproject'' and modify the file ''yourproject.pro''. Add the line
LIBS += -lkdeui
+
<syntaxhighlight lang="cmake">
 +
LIBS += -lkdeui
 +
</syntaxhighlight>
 +
 
 +
== KDevelop 4 ==
 +
 
 +
Using KDevelop 4 to develop KDE projects is pretty straightforward. You can refer to the KDevelop manual (see http://userbase.kde.org/KDevelop4/Manual) for help on how to use KDevelop in general. This section just covers a few things which are nice for KDE applications in particular.
 +
 
 +
=== Fetch source code from git ===
 +
The Project -> Fetch project... menu allows you to easily clone a KDE project repository, by just selecting "KDE" and typing the project name.
 +
 
 +
=== Import a repository you already cloned into KDevelop ===
 +
To do this, just go to Project -> Open/Import project, and select the top-level CMakeLists.txt file from the repository you want to work on.
 +
 
 +
{{tip|When you work on libraries, you first need to install them before you can test or debug your changes.
 +
Since this is cumbersome and time consuming, you should create symlinks ''(ln -s)'' pointing from the build directory to the installation directory for all affected libraries.
 +
 
 +
Often, even simple programs use libraries internally, for example the settings dialog of Konsole is really a library.}}

Latest revision as of 16:01, 23 June 2013

Contents

[edit] Eclipse

KDE4's ktimetracker loaded as eclipse project

This describes how to use Eclipse to develop KDE 4 applications. It has been tested with Eclipse Ganymede and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use KTimeTracker from the kdepim module, other applications should work likewise.

Using this description you will be able to

  • update your working copy of KDE source code using the svn command
  • build your KDE module using CMake
  • build your KDE application from within Eclipse using Make
  • compile and run your application with one click from Eclipse
  • get auto-completion when editing KDE source code
  • have an overview and navigation about your classes within Eclipse
  • have call trees for your functions

[edit] Set up Eclipse with KDE

  • Check your requirements
Trying with a virtual machine I had problems starting Eclipse with less than 1 GB RAM. After assigning 3 GB RAM to the virtual machine, Eclipse finally started.
  • Install Eclipse
Download Eclipse IDE for C/C++ developers from http://www.eclipse.org. Unpack it to /home/user/eclipse.
  • Install the CDT
Download the Eclipse IDE for C/C++ Developers (68 MB) from http://www.eclipse.org/cdt/ and unpack it into your Eclipse folder, in our case /home/user/eclipse.
  • Download kdepim
As said, we use kdepim as example here. So, download ("checkout") kdepim using git (for advanced git-usage see Development/Git/Configuration, especially URL-Renaming):
cd /home/user
git clone git://anongit.kde.org/kdepim
This will check out into /home/user/kdepim. (Our sample setup for this tutorial)
  • Compile kdepim
Compile kdepim so the usual makefiles are present for all kdepim applications. If you have problems doing this, follow our build instructions.
  • Import your project into Eclipse
Surprise: To import your project, you cannot use "File -> Import". Rather do: File -> New -> C++ Project -> Makefile project -> Empty Project -> un-tag "use default location" -> choose /home/user/kdepim/ktimetracker. Call it "ktimetracker".
  • Build your project
Make sure Project -> Properties -> C/C++ Build -> Builder Settings -> Build location -> Build directory is set correctly.
Choose Project -> Build Project
  • Run the project
Choose Project -> Properties -> Run/Debug Settings -> New. As project, enter ktimetracker, as C/C++ Application, enter /home/user/kdepim/ktimetracker/ktimetracker. Choose Apply -> Ok -> Ok. Now you can click on the "Run" button and start it.

[edit] Know-How

[edit] Custom builders

If you want to integrate the CMake build step into your build toolchain, you will need to

  • create a custom builder like this:
echo "cmake . && make -j4 && make install" >/bin/eclipsebuild
chmod 777 /bin/eclipsebuild
  • Add your builder
Choose Project -> Properties -> Builders. Un-tag all existing builders. Click "new" -> Program -> (name it "Builder for KDE"). -> Location: /bin/eclipsebuild -> Working directory /home/user/workspace/myproject1/kdepim.
  • Build
Now you can build your project. Every time you restart eclipse, choose myproject1 -> Project -> Properties -> C/C++ Build -> Ok -> Project -> Build.

[edit] Revert what eclipse did

To revert what eclipse did to your project simply run

rm -rf .externalToolBuilders/ .project .cproject

[edit] Why Subversion does not work

When using Eclipse's svn plugin and building a KDE program, you will get error messages complaining that your svn binary is too old. If you want to try and change this, here is how you get to that error:

  • Install the Subversion plug-ins
Help -> Software Updates -> Available Software -> Add Site -> http://download.eclipse.org/technology/subversive/0.7/update-site/ -> Add Site -> http://www.polarion.org/projects/subversive/download/eclipse/2.0/update-site/
Now add it: Subversive Site -> Subversive SVN Team Provider Plugin
Subversive SVN Connectors Site -> Subversive SVN Connectors -> SVNKit 1.3.0 Implementation (Optional)
  • Click on Install
  • Restart Eclipse
  • Import your KDE module
Choose File -> New -> Other -> SVN -> Project from SVN -> https://svn.kde.org/home/kde/trunk/KDE/kdepim -> Check out as project configured using the New Project Wizard -> C++ Project -> Makefile Project -> Empty Project. As name, we choose kdepim5 -> Finish
  • Set cmake as build environment
Choose Project -> Properties -> C/C++ Build -> Builder Settings. Un-tag "use default build command", set "cmake" instead. Choose Project -> Properties -> C/C++ Build -> Behavior. Replace "all" by ".".

[edit] See also

[edit] QtCreator

KDE4's ktimetracker loaded as QtCreator project

Main article: Development/Tutorials/Using_Qt_Creator

This describes how to use QtCreator to develop KDE 4 applications. It has been tested with QtCreator 1.2.80 and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use ktimetracker from the kdepim module, other applications should work likewise.

[edit] Load an existing project

As discussed here we use ktimetracker as example project.

  • Import the CMakeLists.txt file

File -> Open -> kdepim/CMakeLists.txt.

  • Configure QtCreator to build only ktimetracker

Projects -> ktimetracker -> build settings -> Add a configuration ktimetracker.

As build directory choose kdepim. As arguments for CMake use e.g.

. -DCMAKE_INSTALL_PREFIX=/usr/local -DLIB_SUFFIX=64 -DCMAKE_BUILD_TYPE=debugfull

[edit] Start a KDE project

To start a new project you need to tell QtCreator to use the KDE libraries when building. So, choose File -> New... and create your project. We will call it yourproject here. To be able to use KDE's libraries, go to your home directory, change into yourproject and modify the file yourproject.pro. Add the line

LIBS += -lkdeui

[edit] KDevelop 4

Using KDevelop 4 to develop KDE projects is pretty straightforward. You can refer to the KDevelop manual (see http://userbase.kde.org/KDevelop4/Manual) for help on how to use KDevelop in general. This section just covers a few things which are nice for KDE applications in particular.

[edit] Fetch source code from git

The Project -> Fetch project... menu allows you to easily clone a KDE project repository, by just selecting "KDE" and typing the project name.

[edit] Import a repository you already cloned into KDevelop

To do this, just go to Project -> Open/Import project, and select the top-level CMakeLists.txt file from the repository you want to work on.

Ktip.png
 
Tip
When you work on libraries, you first need to install them before you can test or debug your changes.

Since this is cumbersome and time consuming, you should create symlinks (ln -s) pointing from the build directory to the installation directory for all affected libraries.

Often, even simple programs use libraries internally, for example the settings dialog of Konsole is really a library.

This page was last modified on 23 June 2013, at 16:01. This page has been accessed 12,708 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