https://bugs.kde.org/show_bug.cgi?id=371747
Bug ID: 371747
Summary: Parsing problems propagate up the whole include-tree.
Product: kdevelop
Version: 5.0.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: olaf.the.lost.vik...@gmail.com
Target Milestone: ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
