search

swig / cccl

Unix cc compiler to Microsoft's cl compiler wrapper
GNU General Public License v3.0
123 stars 36 forks source link

README: get rid of MinGW? #8

Closed Artoria2e5 closed 2 years ago

Artoria2e5 commented 3 years ago

The old MinGW is very inactive1 -- even its domain has expired. Its more active fork MinGW-w64 mainly focuses on building toolchains for distributions to package, and on Windows the two would be MSYS2 and Cygwin.

1 You can't quite call it dead, since the OSDN page is technically kicking with the new GCC releases, and people are actually talking on the mailing list. But they still haven't done 64-bit, which isn't much of a good sign in 2021.

I recommend removing references to MinGW in the README. The references can optionally be replaced with MSYS2 if someone wants to test it -- it's bascially Cygwin but lighter and easier to install packages (via pacman).

GitMensch commented 2 years ago

MSYS2 is still much more heavy than MinGW+MSYS. And as cccl uses whatever VC setup is active you can perfectly use "simple old MinGW+MSYS" + cccl + VC 64bit.

So I'd vote for a "no" answer and close this issue.

wsfulton commented 2 years ago

Any Unix-like system will work. I've updated the README to reflect this.

cccl and MinGW-w64 and MSYS2 is used by SWIG on Appveyor, so does work.