This diff adds support for relative roots to VFS overlays. The directory root
will be made absolute from the current working directory and will be used to
determine the path style to use. This supports the use of VFS overlays with
remote build systems that might use a different working directory for each
compilation.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This LGTM but I'm interested to hear from folks with more knowledge about the VFS' desired behavior to comment on if this will have any unexpected side effects
I haven't reviewed the patch, but looking at the description I don't have concerns with this.
@benlangmuir or @vsapsai, any thoughts from you?
Each VFS may have its own working directory, so it could be surprising if we use the OS working directory instead of that. This is complicated by the fact the VFS working directory may not be set yet during parsing the yaml (I haven't checked). I'm not really sure what to recommend here. If we do change this, we should document the new behaviour in the doc comment for RedirectingFileSystem though.
I don't believe the working directory will be set on the VFS at this point, no. If you're happy with the change then i'll update the header docs to describe this behaviour, unless there is another way to achieve using relative paths for root entries in the overlay yaml?
Make sure the test failure gets fixed, but otherwise LGTM.
x64 debian > LLVM-Unit.Support/_/SupportTests::VFSFromYAMLTest.RelativePaths