https://bugs.kde.org/show_bug.cgi?id=360074
Bug ID: 360074
Summary: Include paths detected wrongly with clang and libc++
Product: kdevelop
Version: 4.90.91
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: john5...@gmail.com
When i use clang with libc++, KDevelop still uses the libstdc++ headers causing
all kinds of problems with library types that aren't yet included in libstdc++.
After an initial investigation i am guessing the include paths are discovered
from GccLikeCompiler::includes. Unfortunately using "clang++ -E -v" only shows
the default settings that clang was compiled with, which is the libstdc++
setup.
Using "clang++ -Wp,-v" however shows the include paths that are actually used.
The same options also work for g++ too. The only problem is that it then
expects an input file so i would suggest "clang++ -Wp,-v dummy.cpp
-fsyntax-only"
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
