From KDE UserBase Wiki

KDevelop4 FAQs



This screencast shows you how to get started with a new project, how to build and execute it as well as do basic debuggging.

How do I do start new console application?

Go to Project -> New from template. Select C++ -> No GUI (Cmake) -> Simple CMake-based C++ application and edit the name on the bottom of the window and click Next.

Then appears Version Control System. Select None and click Finish.

Then it asks you to configure build. Click Ok. Now you should have new project visible on Projects list. You can build it by pressing F8 or selecting Project -> Build Selection.

To debug an application you must add launch configuration. This is done from Run-> Configure Launches.

Add new launch by pressing +. You need to edit the Project Target field to point a executable binary. It is same as your project name usually. Or you can just select executable to point the binary. You can also edit the launch name to be more informative than New Native Application Configuration by selecting it on left Launch Configurations list and pressing F2. Apply changes pressing Ok. Then you can add breakpoint to source code with right click -> Toggle Breakpoint. Debugging starts with Run -> Debug launch. On bottom of the screen you can select gdb console tab, and you can use enter commands gdb console.

How do I import an existing project?

Go to Project -> Open/Import project and select the folder of your project. Alternatively select your main makefile or CMakeLists.txt. Follow the wizard.

How do I setup KDevelop to run my application?

Go to Run -> Configure Launches, select your project to the left, press the plus-button. Make sure the type of the new launch configuration (give it a proper name!) is Native Application. Now go to the Project target field to the left and type in the path to your target. Start with your projects name, it has auto completion.


We are well aware that this is a mess and needs to be improved...

How do I debug my application in KDevelop?

If you setup a launch configuration (see above) you should be able to run that in debug mode as well.


Make sure you build with debug symbols enabled. The default for new CMake projects is the Debug type, hence it should hopefully work out-of-the-box.

How do I get pretty printed variable contents while debugging?

Make sure your ~/.gdbinit looks similar to this:

import sys
sys.path.insert(0, '/home/milian/projects/compiled/kde4/share/apps/kdevgdb/printers')

from qt4 import register_qt4_printers
register_qt4_printers (None)

from kde4 import register_kde4_printers
register_kde4_printers (None)

from libstdcxx import register_libstdcxx_printers
register_libstdcxx_printers (None)


Of course you have to adapt the path to point to the pretty printers.

What kind of build environments does KDevelop 4 support?

cmake, any other make-file based project via custom makefile, generic...

How do I use Subversion from within KDevelop 4?

For subversion support you need to have it enabled on compile time. If that is the case, then you can right click your project files and find subversion item from the pop-up menu. There you can find common tasks, like Update and Commit.

Where is search/replace in files ?

Starting with version 4.2, KDevelop ships by default with a search/replace in files plugin. Access it via the menu or from the context menu, e.g. in project view or on a selection in the editor.

How can I special-case C/C++ code specifically for KDevelop?

The C/C++ support for KDevelop defines the macros IN_KDEVELOP_PARSER and IN_IDE_PARSER which you can use in your source code as required to workaround limitations or define custom macros etc.

What are workingsets and how do I use them?


How to add include or library directory to compile option?

This depends on your build toolchain (CMake, QMake, autotools, ...), please refer to the documentation thereof. There is a CMake tutorial for example.

For cases where KDevelop is still not figuring out the include path properly after you have configured your build toolchain, you can manually add include paths on a per-directory basis into a .kdev_include_paths file. This can be done from inside KDevelop by running the "solve problem" wizard associated with a "could not find include file" problem, e.g. by hovering the problematic #include line.