Yes, on Windows WCHAR_T is always 16 bits. That's why the MS compiler does not understand...
Well, -fshort-wchar does not apply to Visual Studio compiling, as far as i remember....
If your goal is a successful Windows build then use the Visual Studio solution. Nothing...
With the attached test.xml file (encoded in UTF-8) I can duplicate the issue using...
If your goal is a successful Windows build then use the Visual Studio solution. Nothing...
The included Visual Studio solution should build fine under vs 2013 and vs 2015....
With the attached test.xml file (encoded in UTF-8) I can duplicate the issue using...
xmlwf always uses the UTF-8 version of libexpat, even on Windows. So this issue can't...