llvm-project/clang/test/VFS/Inputs/some_frame_module.map

framework module SomeFramework {
  umbrella header "public_header.h"
  export *
  module * { export * }
}
Stopgap fix for finding module for a file mapped in the VFS If we lookup a path using its 'real' path first, we need to ensure that when we run header search we still use the VFS-mapped path or we will not be able to find the corresponding module for the header. The real problem is that we tie the name of a file to its underlying FileEntry, which is uniqued by inode, so we only ever get the first name it is looked up by. This doesn't work with modules, which rely on a specific file system structure. I'm hoping to have time to write up a proposal for fixing this more permanently soon, but as a stopgap this patch updates the name of the file's directory if it comes from a VFS mapping. llvm-svn: 209534 2014-05-24 02:15:47 +08:00			`framework module SomeFramework {`
			`umbrella header "public_header.h"`
			`export *`
			`module * { export * }`
			`}`