honkstar1 wrote:
I'm working with Neil and I've just tried changing our system to work the way
where all our rsp etc use virtual paths and then create a vfsoverlay that
points to the "right" places... it almost works for portable pch.
What is not working is "#include_next".. that gets resolved to a non-virtual
path which is written into the .pch and .d files. For example this file:
Unix\LibCxx\include\c++\v1\stddef.h has "#include_next "
Are there any options to control that?
https://github.com/llvm/llvm-project/pull/106577
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits