Dieser Screencast zeigt, wie man mit einem neuen Projekt startet, wie man es baut und ausführt, sowie die Grundzüge des Debuggens.
Go to. Select and edit the name on the bottom of the window and click .
Then appears. Select and click .
Then it asks you to configure build. Click F8 or selecting .. Now you should have new project visible on list. You can build it by pressing
To debug an application you must add launch configuration. This is done from.
Add new launch by pressing F2. Apply changes pressing . Then you can add breakpoint to source code with . Debugging starts with . On bottom of the screen you can select tab, and you can use enter commands gdb console.. You need to edit the 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 by selecting it on left list and pressing
Go toand select the folder of your project. Alternatively select your main makefile or CMakeLists.txt. Follow the wizard.
Go to, select your project to the left, press the plus-button. Make sure the type of the (give it a proper name!) is . Now go to the field to the left and type in the path to your target. Start with your projects name, it has auto completion.
|Wir sind uns im Klaren darüber, dass das das verbessert werden mus ...|
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 thetype, hence it should hopefully work out-of-the-box.|
Stelle sicher, dass dein ~/.gdbinit ähnlich zu diesem ist:
python 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) end
Of course you have to adapt the path to point to the pretty printers.
cmake, any other make-file based project via, generic...
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 finditem from the pop-up menu. There you can find common tasks, like and .
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.
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.
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