https://bugs.kde.org/show_bug.cgi?id=386421
--- Comment #7 from Sven Brauch ---
I think the thing is that clang simply doesn't suggest local includes
(specified with -I) when typing #include < even though the resulting code would
still be compiling. Since we specify all your
https://bugs.kde.org/show_bug.cgi?id=386421
--- Comment #6 from Venca B Spam ---
Ok, I got it.
I have observation that in some cases when the include is already written e.g.
```code
#include
```
The included file can be "clicked-through" (Ctrl+LMB on the included file)
https://bugs.kde.org/show_bug.cgi?id=386421
--- Comment #5 from Sven Brauch ---
It's not that simple, we can retrieve information from the build system but we
assemble the compiler command line ourselves. We also add your hand-configured
includes etc. and that code, from a
https://bugs.kde.org/show_bug.cgi?id=386421
--- Comment #4 from Venca B Spam ---
I did not dig into details (yet) however I was thinking that as long as
KDevelop is using Clang as backend for C++ language support (code completion &
friends), it does not play a role.
I mean,
https://bugs.kde.org/show_bug.cgi?id=386421
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
---
https://bugs.kde.org/show_bug.cgi?id=386421
Venca B Spam changed:
What|Removed |Added
Version|5.1.80 |5.2.0
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=386421
--- Comment #1 from Venca B Spam ---
Created attachment 108662
--> https://bugs.kde.org/attachment.cgi?id=108662=edit
Sample project required to reproduce reported behavior.
--
You are receiving this mail because:
You are