Using nimterop in MSYS2 Bash environment on Windows about nimterop HOT 3 CLOSED

Sorry it's been a while since I've done this but there might be a way to discriminate between MSYS and MinGW. Maybe the MSYSTEM variable?

from nimterop.

Nice idea, maybe $MSYSTEM detection is the way to go. I tried echo'ing it in Bash shells for various MSYS2 environments:

• MSYS MSYS2 environment, $MSYSTEM is MSYS
• MINGW64 MSYS2 environment, $MSYSTEM is MINGW64
• MINGW32 MSYS2 environment, $MSYSTEM is MINGW32
• UCRT64 MSYS2 environment, $MSYSTEM is UCRT64
• ...

By default (at least when checking my own Win machines), %MSYSTEM% in cmd.exe is unset, and $env:MSYSTEM in PowerShell is unset.

So maybe it would be enough to check if it's set with the os module's existsEnv? If so, use -G"MSYS Makefiles"; if not, use -G"MinGW Makefiles"?

Would that logic be suitable to wholly replace the uname check in the if findExe("sh").len != 0 branch of when defined(Windows)?

🤔 I feel like I'm probably not appreciating the full variety of environmental conditions that could be in play (e.g. Cygwin vs. MSYS2 UCRT64/whatever), but am not really sure at present.

from nimterop.

I see you already clarified the MSYSTEM question here.

from nimterop.