Qt5/Mac header finding in KDevelop5 (clang parser??)
René J.V. Bertin
rjvbertin at gmail.com
Wed Jun 22 22:28:23 UTC 2016
On Thursday June 23 2016 00:05:15 Milian Wolff wrote:
> errors. Please, pretty please - be more specific (not necessarily more
> verbose), when writing your mails...
I try to be, but it's not easy when you have to figure out the common vocabulary...
> Have a look at clangsupport.cpp, cf. it's importedContextForPosition. That
> relies on the DUChain import structure to find lines that correspond to an
> #include. If you say the code browsing and syntax highlighting works, then the
> import structure in the DUChain should also be correct. Potentially what's
> broken is the check for CXCursor_InclusionDirective in clanghelpers.cpp'
> visitCursor callback. Can you inspect that?
I'll try. Is it possible that syntax highlighting and code browsing continue to function (with #import) because the information is cached? I tried to exclude that by using the reload button in the Problem reporter, without being certain that indeed regenerates all parsing information for the selected file.
> > 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.
> Lack of time is one reason.
What I meant is that changing #include to #import and verifying if code browsing and syntax highlighting still works doesn't take more than a few seconds for anyone who has a project open in KDevelop anyway. Figuring out why "context browsing" doesn't work with #import is a different thing
More information about the KDevelop-devel