mstorsjo wrote: > Second, to support libc++, the STL headers must be separated into its own > directory to prevent header conflicts. Therefore, this must be resolved > jointly by Clang driver and the sysroot script.
What's the practical difference here, between just providing the libc++ includes in a path that is searched before the main MSVC include directory? (One difference that comes to mind is that it doesn't accidentally use an STL header if libc++ doesn't provide a corresponding one.) It's worth remembering that libc++ in MSVC mode practically still is layered on top of STL/vcruntime for some of the lower level bits. https://github.com/llvm/llvm-project/pull/96417 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
