Displaying 3 results from an estimated 3 matches for "b8bf13bd".
2011 Sep 02
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Nikola,
Your patchset does not work;
e>bin\clang.exe -S なかむら\たくみ.c
error: error reading '邵コ・ェ邵コ荵昴・郢ァ蝎らクコ貅假ソ・邵コ・ソ.c'
1 error generated.
- Would it be not enough in somewhere?
I suspect clang still might be pathv1-dependent.
(I guess, pathv1 would assume ansi)
- raw_ostream does not handle utf8, but ansi, on win32.
I would like to propose;
- converting utf8 and utf16
2011 Sep 02
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...oes not work;
>
> e>bin\clang.exe -S なかむら\たくみ.c
> error: error reading '邵コ・ェ邵コ荵昴・郢ァ蝎らクコ貅假ソ・邵コ・ソ.c'
> 1 error generated.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110902/b8bf13bd/attachment.html>
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
AFAIK Clang internals do assume utf8, and llvm::sys::path converts strings
to utf16 on windows and calls W API functions.
If somebody would like to take a look at my changes and comment on them.
Here's a brief explanation of what I did:
- Convert argv to utf8 using current system locale for win32 (this is done
as soon as possible inside ExpandArgv). This makes the driver happy since
calls to