[Differential] [Request, 20 lines] D2649: MissingIncludeAssistant: use the compilation unit as a path
nicolaih (Nicolai Hähnle)
noreply at phabricator.kde.org
Sun Sep 4 12:36:46 UTC 2016
nicolaih created this revision.
Restricted Application added a subscriber: kdevelop-devel.
For the purpose of determining where custom defines and includes should
be added, the final location of the diagnostic is irrelevant: it's the
path to the compilation unit itself that matters, since that's where the
corresponding configuration is taken from.
If you have a missing include file in an include file, compilationUnit()
gives the path in which a custom include should be added, unlike
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel