include-what-you-use | Automated svn2git mirror of include-what-you-use : link

Include-what-you-use makes heavy use of Clang internals, and will occasionally break when Clang is updated. See the include-what-you-use Makefile for instructions on how to keep them in sync. IWYU, like Clang, does not yet handle some of the non-standard constructs in Microsoft’s STL headers. A discussion on how to use MinGW or Cygwin headers with IWYU is available on the mailing list. We support two build configurations: out-of-tree and in-tree.
If you’re building IWYU out-of-tree or installing pre-built binaries, you need to make sure it can find Clang built-in headers (stdarg.h and friends.). Clang’s default policy is to look in path/to/clang- executable/../lib/clang/<clang ver>/include. So if Clang 3.5.0 is installed in /usr/bin, it will search for built-ins in /usr/lib/clang/3.5.0/include. Clang tools have the same policy by default, so in order for IWYU to analyze any non-trivial code, it needs to find Clang’s built-ins in path/to/iwyu/../lib/clang/3.5.0/include where 3.5.0 is a stand-in for the version of Clang your IWYU was built against. This weirdness is tracked in issue 100, hopefully we can eliminate the manual patching.