On Thu, 8 Jun 2023, LIU Hao wrote:
There are also builds with clang, but clang expects UCRT anyway
This statement is untrue.
* MSYS2: https://github.com/msys2/MINGW-packages/blob/bf2ba8f4bba3d14fdaa2572cffb4abd4e6791246/mingw-w64-crt-git/PKGBUILD#L65
Yes, the msys2 "clang*" environments are UCRT based. But you can also install and use Clang in the msys2 "mingw64" environment just fine:
https://packages.msys2.org/package/mingw-w64-x86_64-clang?repo=mingw64
* llvm-mingw: https://github.com/mstorsjo/llvm-mingw/blob/7e8bcdc43c8b68dd25d39e583cb41dc21a0d6c22/build-mingw-w64.sh#L20
This is just a default for when whoever builds it doesn't set another preference.
I regularly test llvm-mingw with msvcrt too; for my local nightly builds, I use a rotating schedule, alternating the --with-default-msvcrt option between ucrt, ucrtbase and msvcrt. So if there's blocking breakage within either of them, I'll run into it within 3 days at most.
This includes testing the armv7/aarch64 targets with msvcrt, even if that's a rather contrieved setup that nobody probably would use in practice. But the toolchains that are built to default to msvcrt, also work for armv7/aarch64.
I also do a subset of releases that are based on msvcrt: https://github.com/mstorsjo/llvm-mingw/releases/tag/20230603 So Clang doesn't have any specific requirement assuming UCRT. // Martin _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
