[Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

[Liang Qi]

http://doc.qt.io/qt-5/supported-platforms.html
msvc 2013 is still supported in 5.8

http://doc.qt.io/qt-5.6/supported-platforms.html
msvc 2010/2012/2013 are still supported in 5.6

Compiler options for msvc 2015: https://msdn.microsoft.com/en-us/library/fwkeyyhe.aspx
Compiler options for msvc 2013: https://msdn.microsoft.com/en-us/library/fwkeyyhe(v=vs.120).aspx

If not all supported compilers support /utf-8 or similar options, what should be done next step?

Best Regards,
Liang

> On 30 Jan 2017, at 17:30, Thiago Macieira <thiago.macieira at intel.com> wrote:
> 
> On segunda-feira, 30 de janeiro de 2017 09:56:46 PST Giuseppe D'Angelo wrote:
>> Il 30/01/2017 02:21, Thiago Macieira ha scritto:
>>> So, we should:
>>> a) still avoid non-ASCII in our source files, aside from comments
>>> b) allow non-ASCII in comments, as needed
>> 
>> Didn't we have issues with UTF-8 in comments too, when using MSVC?
> 
> Yes, which means that if it chokes on KDAB's name in qglobal.h, too bad.
> 
>>> c) turn the -utf-8 option on for MSVC2015U3.
>> 
>> But just for Qt own build, not push this option onto the users. Also,
>> does this fix anything? Is MSVC 2015 U3 the only one complaining, and we
>> can live with UTF-8 in the source when using other compilers?
> 
> This will affect the Qt build only. Only MSVC 2015 U3 gets the fix, the older 
> versions and MSVC 2013 will still be affected.
> 
> Sorry, tough luck for the others.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development