thakis added a comment. In http://reviews.llvm.org/D12646#241318, @hintonda wrote:
> In http://reviews.llvm.org/D12646#241308, @kubabrecka wrote: > > > In what scenario exactly are you seeing an issue? If it's a just-built > > clang that can't find C++ headers, then you should just build the libcxx > > project alongside. > > > clang++ defaults to -stdlib=libc++ for newer versions of MacOS (see > ToolChains.cpp:902), but since there isn't a way to pass corresponding > include path via cmake, clang++ doesn't work out of the box, i.e., it only > checks /usr/include/c++/v1, not the path relative to the version of clang > used to build it. > > I first noticed it when I tried to run the version of clang-tidy I'd just > built and found I had to pass the path for it to find iostream. I think it works if you a) check out libcxx into llvm/projects/libcxx b) run `make install` and c) run the binary from your install directory. http://reviews.llvm.org/D12646 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
