| commit | 6dbcbbcfcdcc44c8f7641dc788d2523cf1a09b5b | |
| author | Argiris Kirtzidis <akyrtzi@gmail.com> | |
| Wed, 3 Nov 2010 22:45:23 +0000 (3 22:45 +0000) | ||
| committer | Argiris Kirtzidis <akyrtzi@gmail.com> | |
| Wed, 3 Nov 2010 22:45:23 +0000 (3 22:45 +0000) | ||
| tree | fee8c776b8591a09c1387bcc7dd3bd1bccb14e7e | treesnapshot (tar.gz zip) |
| parent | 1ecda74bf22dbfbdf7c7c62b9b13c9011464d11a | commitdiff |
Implement -working-directory.
When -working-directory is passed in command line, file paths are resolved relative to the specified directory.
This helps both when using libclang (where we can't require the user to actually change the working directory)
and to help reproduce test cases when the reproduction work comes along.
--FileSystemOptions is introduced which controls how file system operations are performed (currently it just contains
the working directory value if set).
--FileSystemOptions are passed around to various interfaces that perform file operations.
--Opening & reading the content of files should be done only through FileManager. This is useful in general since
file operations will be abstracted in the future for the reproduction mechanism.
FileSystemOptions is independent of FileManager so that we can have multiple translation units sharing the same
FileManager but with different FileSystemOptions.
Addresses rdar://8583824.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@118203 91177308-0d34-0410-b5e6-96231b3b80d8
When -working-directory is passed in command line, file paths are resolved relative to the specified directory.
This helps both when using libclang (where we can't require the user to actually change the working directory)
and to help reproduce test cases when the reproduction work comes along.
--FileSystemOptions is introduced which controls how file system operations are performed (currently it just contains
the working directory value if set).
--FileSystemOptions are passed around to various interfaces that perform file operations.
--Opening & reading the content of files should be done only through FileManager. This is useful in general since
file operations will be abstracted in the future for the reproduction mechanism.
FileSystemOptions is independent of FileManager so that we can have multiple translation units sharing the same
FileManager but with different FileSystemOptions.
Addresses rdar://8583824.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@118203 91177308-0d34-0410-b5e6-96231b3b80d8
38 files changed: