Qt5/Mac header finding in KDevelop5 (clang parser??)

René J.V. Bertin rjvbertin at gmail.com
Wed Jun 22 15:36:49 UTC 2016

On Wednesday June 22 2016 16:42:11 Milian Wolff wrote:

> We use libclang, we don't do anything ourselves. If it works in clang, then we 
> maybe just miss a setting or commang line parameter to enable the feature.

Do you also get the header file paths from libclang? From what I can tell the parser indeed gets the definitions from those files but the editor doesn't know which file to open. IOW, changing #import into #include doesn't change necessarily change anything w.r.t. code colouring, and you can jump to a type's definition in that headerfile via the code browser with both directives. The change only means you can open the header via a right-click on the include directive.
Changing say a Qt header include to "#import <QtFoo> has the opposite effect, everything still works except opening the headerfile from the include directive.

I cannot check right now but I see no reason why it wouldn't be the same on Linux. It's easy enough to verify for anyone.


More information about the KDevelop-devel mailing list