2016-01-13 18:08 GMT+01:00 LM:
> Jan Nijtmans wrote:
>> However, I would recommend to use MinGW-w64, then you
>> can use all unicode characters in the command line you like
>
> A lot of die-hard original MinGW users including myself refuse to use
> MinGW-w64 due to licensing related issues. I feel everyone should be
> able to use the tools/utilities/compilers they're most comfortable
> with. I'm perfectly happy with my own MinGW fork and it does a few
> things that MinGW-w64 can't.
I'm sure that's true. In my opinion, Fossil builds better with MinGW-w64
than with MinGW because the lack of UNICODE support in MinGW. See:
<https://sourceforge.net/p/mingw/bugs/771/>
If MinGW would support UNICODE applications (as MSVC and
MinGW-w64 do), then those lines in Fossil could be simplified:
<http://www.fossil-scm.org/index.html/artifact/5cbae19db27ca153?ln=584-592>
Pity for Fossil, this MinGW bug #771 is already open for almost 10 years,
and I don't see any progress on it. :-(
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
