Add [mingw-w64-x86_64-gcc-libs-devel]

[lygstate]

Package name

mingw-w64-x86_64-gcc-libs-devel

Brief description of package

Split mingw-w64-x86_64-gcc-libs-devel out of mingw-w64-x86_64-gcc, So that when using clang with mingw-w64-x86_64, there is no need install mingw-w64-x86_64-gcc, This is used to reduce the downloading size for container.

URL for package's homepage

https://packages.msys2.org/package/mingw-w64-x86_64-gcc?repo=mingw64

Provide a basic test case to validate the package's functionality.

No response

MINGW environments where you need the package

• [X] MINGW64
• [X] MINGW32
• [X] UCRT64
• [X] CLANG64
• [X] CLANG32
• [X] CLANGARM64

Are you willing to submit a PR?

maybe

[Biswa96]

• What should mingw-w64-x86_64-gcc-libs-devel package contain?
• Is there any reason not to use the clang64 or clang32 environment?

[lygstate]

• What should mingw-w64-x86_64-gcc-libs-devel package contain?

The C/C++ runtime libraries and headers, do not contains the gcc compiler(they are redundant to clang)

• Is there any reason not to use the clang64 or clang32 environment?

mingw-w64-x86_64-gcc have more broader usage currently, also clang64 vs mingw-w64-x86_64 mainly is CRT differencies not the compiler differences(gcc not work with is bacause gcc doesn't support that),

[kmilos]

gcc not work with is bacause gcc doesn't support that

GCC works fine in the (now recommended/default) UCRT64 environment.

[lazka]

I guess this makes sense, but not sure if it's worth the added complexity.