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

            Bug ID: 389550
           Summary: C/C++ language support sometimes fail to resolve
                    included files when include file itself has never been
                    included.
           Product: kdevelop
           Version: 5.2.1
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Language Support: CPP (Clang-based)
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: vbs...@centrum.cz
  Target Milestone: ---

C/C++ language support sometimes fail to resolve include files when include
file itself has never been included.

* How to reproduce? *

1. Download attached sample test case project
2. Follow steps on the video bug report attached. Shortly:
 - Start fresh new KDevelop session
 - Open the project attached and let the background parser finish its job
 - Open the include file "Bar/Bar.hpp"
 - Observe the line with "Thirdparty/Interface.hpp" inclusion

* What happens? *

Although the #include directive is correct in the context of the build system,
KDevelop marks the line as not only problem (which is incorrect) it also do not
use the "Thirdparty/Interface.hpp" for further language analyse.

* What is expected? *

Even if the include file is not actually never included, it should be properly
parsed. KDevelop should not generate confusing false error positives.

* Observation *

When the include file "Bar/Bar.hpp" is included in another file (e.g. Foo.cpp),
the problem disappears (demonstrated on the video attached).

Also later when is such inclusion removed (from Foo.cpp) the problem does not
reappear.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to