You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MSYS2 has a gui that lets you select between MSYS2, mingw32, and mingw64. The latter two work, but MSYS2 is broken. It looks like they're going for it being a "unix" because unix is defined, but it also defines __CYGWIN__. We could try to compile it as either linux or windows. When I try to compile as Windows it gets pretty far with some minimal changes. Building it as linux hits many more errors.
The Windows build is missing _wfopen and _wfopen_s which means no unicode filenames can be opened. So it's pretty broken all around. I don't know a use case for supporting MSYS2 standalone, but I did some work looking into it so here are the findings.
MSYS2 is for building Unix-like targets with Unix-like tools on Windows, for Windows, using the native Windows runtime. It will allow you to run GCC etc.., more specificallly, the Mingw32 and Mingw64 targets. You still need to use the Windows API, although many of the standard "Unix" C library stuff, is implemented. It's very useful, and I use it all the time and prefer it over the Microsoft tools.
MSYS2 has a gui that lets you select between MSYS2, mingw32, and mingw64. The latter two work, but MSYS2 is broken. It looks like they're going for it being a "unix" because unix is defined, but it also defines
__CYGWIN__
. We could try to compile it as either linux or windows. When I try to compile as Windows it gets pretty far with some minimal changes. Building it as linux hits many more errors.The Windows build is missing
_wfopen
and_wfopen_s
which means no unicode filenames can be opened. So it's pretty broken all around. I don't know a use case for supporting MSYS2 standalone, but I did some work looking into it so here are the findings.The text was updated successfully, but these errors were encountered: