https://bugs.kde.org/show_bug.cgi?id=393779
--- Comment #24 from Milian Wolff <m...@milianw.de> --- Git commit 169371b5d3448949122d5846c7da29ab86b1a0e9 by Milian Wolff. Committed on 04/05/2018 at 15:26. Pushed by mwolff into branch 'master'. Allow overriding the path to the builtin clang compiler headers The current code to detect the path for the builtin clang compiler headers fails on Gentoo. Allow setting the KDEV_CLANG_BUILTIN_DIR environment variable for such cases as a stop-gap measure to workaround this for now. We will have to find a better approach to this problem, it seems. Most notably, we will probably have to detect the path at runtime based on the libclang we actually use then. This may be different from the one we compiled against... For now, we also report an error (only visible on the command line) when the KDEV_CLANG_BUILTIN_DIR path is "wrong", i.e. doesn't contain the varargs.h header. In such cases, we disable the kdev-clang plugin, since it would be unusable anyways. M +10 -0 plugins/clang/clangsupport.cpp M +7 -0 plugins/clang/duchain/duchainutils.cpp M +1 -0 plugins/clang/duchain/duchainutils.h M +3 -2 plugins/clang/duchain/parsesession.cpp https://commits.kde.org/kdevelop/169371b5d3448949122d5846c7da29ab86b1a0e9 -- You are receiving this mail because: You are watching all bug changes.
