forked from OSchip/llvm-project
879c15e890
When llvm-rc loads an external file, it looks for it relative to a number of include directories and the current working directory. If the path is considered absolute, llvm-rc tries to open the filename as such, and doesn't try to open it relative to other paths. On Windows, a path name like "\dir\file" isn't considered absolute as it lacks the drive name, but by appending it on top of the search dirs, it's not found. LLVM's sys::path::append just appends such a path (same with a properly absolute posix path) after the paths it's supposed to be relative to. This fix doesn't handle the case if the resource script and the external file are on a different drive than the current working directory; to fix that, we'd have to make LLVM's sys::path::append handle appending fully absolute and partially absolute paths (ones lacking a drive prefix but containing a root directory), or switch to C++17's std::filesystem. Differential Revision: https://reviews.llvm.org/D92558 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| absolute.test | ||
| codepage.test | ||
| cpp-output.test | ||
| flags.test | ||
| helpmsg.test | ||
| include-paths.test | ||
| language.test | ||
| memoryflags-stringtable.test | ||
| memoryflags.test | ||
| not-expr.test | ||
| parser-expr.test | ||
| parser.test | ||
| tag-accelerators.test | ||
| tag-dialog.test | ||
| tag-escape.test | ||
| tag-html.test | ||
| tag-icon-cursor.test | ||
| tag-menu.test | ||
| tag-stringtable.test | ||
| tag-user.test | ||
| tag-versioninfo.test | ||
| tokenizer.test | ||
| versioninfo-padding.test | ||