Get Involved/development/IDE configuration/KDevelop: Difference between revisions

From KDE Community Wiki
m (Split into sections)
(Use link to moved page)
Tag: Replaced
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
KDevelop is an IDE from KDE.
Moved to https://develop.kde.org/docs/getting-started/building/ide/kdevelop/
 
A screen recording version is available https://www.youtube.com/watch?v=LcSfUNrd3S4
 
== kdesrc-build ==
 
Make sure kdesrc-build works correctly. Make sure ~/.config/kdesrc-buildrc contains the lines:
 
{{Input|1=<nowiki>
cmake-options -DCMAKE_BUILD_TYPE=Debug
</nowiki>}}
 
Using kdesrc-build build a module. E.g.
{{Input|1=<nowiki>
kdesrc-build bluez-qt
</nowiki>}}
 
== Importing a kdesrc-build project into KDevelop ==
 
E.g. on Kubuntu 22.04.
{{Input|1=<nowiki>
apt install kdevelop clazy heaptrack
</nowiki>}}
 
Start kdevelop. From the kdevelop main menu Session > make sure that you have a new/clean session. E.g. Delete Current Session...
 
From kdevelop main menu > Project > Open/Import Project... Name: /home/n/kde/src/bluez-qt/CMakeLists.txt > Next > Finish. If it asks to Override, override.
 
A dialog is shown: Configure a Build Directory for bluez-qt. It will guess all of the values: Build directory: /home/n/kde/build/bluez-qt. "Using an already created build directory.". Installation prefix: /home/n/kde/usr. Build type: Debug. CMake executable: /usr/bin/cmake. Press OK button.
 
== Adding breakpoints ==
 
From kdevelop main menu > Window > Tool Views > Projects. Expand the treeview to one of the entrypoints (CMake targets). E.g. bluez-qt > autotests > managertest > managertest.cpp. The file "/home/n/kde/src/bluez-qt/autotests/managertest.cpp" will be opened in the text editor view.
 
Navigate to the method "bluezNotRunningTest()", put a breakpoint on the line with "{" (the opening curly bracket of the method). Right click on the line > Toggle Breakpoint.
 
In Projects view, right click on the CMake target "managertest" > Debug As... > Compiled Binary.
 
An error will be shown "Could not start debugger. Could not run 'lldb-mi'. Make sure that the path name is specified correctly.". From kdevelop main menu > Settings > Configure KDevelop... > Plugins >  Debugging > uncheck "LLDB Support" > OK.
 
Navigate to method "bluezNotRunningTest()", put a breakpoint on the line with "{" (the opening curly bracket of the method). Right click on the line > Toggle Breakpoint.
 
In Projects view, right click on the CMake target "managertest" > Debug As... > Compiled Binary.
 
The debugger starts and breaks on the first line of C++ source code after the breakpoint. From the main menu > Run > Step Over (F10)/Step Into (F11)/Step Out (F12).

Latest revision as of 17:42, 18 April 2024