[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kdevelop] [Bug 287492] Qt includes are not offered in #include <QFoo> form
From:       Kevin Funk <kevin () kfunk ! org>
Date:       2014-01-29 19:33:21
Message-ID: bug-287492-17878-6BjF6sCOTv () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=287492

--- Comment #9 from Kevin Funk <kevin@kfunk.org> ---
Apparently that's really problem of using self-compiled Qt and using one from
/usr/include.

The subtle difference: In self-compiled Qt: The header QState includes
"qstate.h" which again includes something like
"../../../../src/qt/src/corelib/statemachine/qstate.h". Hence, the QState file
is not considered an direct importer of 
"../../../../src/qt/src/corelib/statemachine/qstate.h" and is discarded.

In Cpp::missingIncludeCompletionItems:
decl->topContext()->parsingEnvironmentFile()->importers() only returns files
such as '/path/to/qstate.h'.

Apparently DUContextDynamicData::addImportedChildContext is responsible for
"sorting" out indirect imports. Does that make sense? Even if it does, I don't
know how to fix. This is quite internal stuff.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]