I have a project which has to use Intel Pin. But I am sure you can find many projects like this, so please take this just as an example. Deep into the include-tree of Pin there is a config.h file that includes further headers depending on DEFINES. F.ex.: #if !defined(FUND_TC_HOSTCPU) # include "fund/config-hostcpu.h" #endif This is not a problem when building as the build system sets the correct values, but KDevelop cannot parse the whole project (which has to include the "top" header <pin.H>) because this config-hostcpu.h file doesn't exist. I solved this for now by just providing DEFINES (which I hope are correct...) in the project settings. But I don't think this should be mandatory for users to go through (sometimes huge) external projects, understand their include/define magic and guess (probably wrong) values to manually add to the project. KDevelop could f.ex. accept it doesn't understand/cannot parse a certain header (and of course showing "Problems" when opening that!) but not propagate these errors into the parsing of my own files. This is probably connected to bug #371741.
Thank you for reporting this bug 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!