You are not logged in.
I create new project and press debug, configured new launcher correctly, but i get this error:
Could not start debugger.
Could not run 'lldb-mi'. Make sure that the path name is specified correctly.
I have installed these packages too but result is same:
cmake gcc clang gdb lldb clazy cppcheck astyle ctags meson ninja
KDevelop 5.10.221201
ArchLinux is installed and updated on 2023-01-20
LXQt desktop with openbox and sddm
Kernel 6.1
Offline
It seems lldb-mi was part of the llvm/lldb project but has been moved out of it.
https://lists.llvm.org/pipermail/lldb-d … 15357.html
There's no lldb-mi pacakge in repos, but aur has https://aur.archlinux.org/packages/lldb-mi-git .
You'll have to build it yourself, check https://wiki.archlinux.org/title/Arch_User_Repository incase you're not familiar with using aur packages.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
It will not work anyway since kdevelop lldb support requires python2
Offline
it seems, to be able to choose gdb, okteta should be installed, after that, i was able to select gdb instead of lldb, then debugging worked, but we can't choose lldb anymore? i hope it will be fixed soon.
i think kdevelop would need to give more informative errors like, "okteta is not found and in order to use gdb, okteta needs to be installed" etc. because i am new to kdevelop and i don't know about details on how it's supposed to work in default settings.
Offline
i think kdevelop would need to give more informative errors like, "okteta is not found and in order to use gdb, okteta needs to be installed" etc. because i am new to kdevelop and i don't know about details on how it's supposed to work in default settings.
On archlinux it's a good idea to use pacman -Qi pkgname after you installed something new.
Especially when things don't go as you expect.
Check the output of
$ pacman -Qi kdevelopand pay attention to the list of optional dependencies and what they're needed for.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline