On Montag, 16. November 2020 02:53:14 CET Thiago Macieira wrote: > On Sunday, 15 November 2020 08:29:56 PST Thiago Macieira wrote: > > > * whether there is any chance to get a fix or workaround in the near > > > future > > > (or even right now), either in the form of an upgrade to the vendor > > > compiler or in the form of a third-party compiler (e.g., GCC or Clang, > > > which both support many platforms). > > > > Probably no chance. > > Sorry, by that I meant to say "no chance of getting a fix in", since it > depends on fixing the Microsoft STL and I don't expect they're very > interested. Their first and foremost priority is the VC++ compiler. > > But the second part of your proposal is easy: use either cl or gcc or clang > (with either libstdc++ or libc++), two combinations of which are supported > by Qt on Windows and I wouldn't be surprised if the rest using those > compilers also worked. > > ✓ VC++ with MS STL (officially supported) > ✓ gcc with libstdc++ (officially supported) > ❓ gcc with libc++ (likely works) I doubt anyone ever tests this combo though.
> ❓ clang with libstdc++ (likely there are people using) > ❓ clang with libc++ (likely works) Is used for fuzzing builds, so I assume actively tested outside our integration. > ✗ clang-cl with MS STL (currently broken) It is? I often use this when building qtwebengine for Windows. Been advocating for an automated test for a while. > ❓❓ clang-cl with libc++ (no clue) You mean clang? Clang-cl.exe is the MSVC compatible clang version, and clang.exe the "gcc" (crossplatform clang) compatible. Which I assume also means thereis clang.exe with libstdc++ for mingw compatible builds. 'Allan _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development