Created attachment 106503 [details] A screenshot of kdevelop showing the parser error in the bottom view with the include being correctly located as reported in the popup over the source code I'm developing a project with Qt5 and CMake. The Qt5 includes are reported as "not found" in the "Problems" view ("Current project" selected as the scope), but, at the same time, when I hover the problematic include in the source code editor, the popup displays the correct full path to the said include, and the symbols that the include defines are correctly imported by the CPP parser. Still, the first angular bracket in the include is underlined with a red wave, which probably is another manifestation of the fact that the problem view reports in issue about the header not being found and a part of the same problem reporting mechanism. Attached are the screenshot of the whole KDevelop window with the CPP parser popup related to the problematic include, and the CMakeLists.txt file for the project. The project builds and runs fine within the same KDevelop session.
Created attachment 106504 [details] CMakelists.txt for the project I'm developing
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!