NEWS: Moving MSYS(2) closer to Cygwin #362
Conversation
lazka
force-pushed
the
news-closer-cygwin
branch
from
59f7718 to
4520961
Compare
There was a problem hiding this comment.
LGTM - I only wished that I would have known this earlier :-)
As a "bonus": it would be interesting to know how "good old msys/mingw" are different to MSYS2 (tripplet, variables, and C/C++ definition) - because "yes" - some programs still need to/want to keep that in mind (msys/mingw is the only option for ancient Windows versions and is much smaller overall [and obviously: outdated])
I've never used old MSYS, so that would require some archeology ;) |
| The next planned steps for this transition are currently: | ||
|
|
||
| * Change the default host triplet from "x86_64-pc-msys" to "x86_64-pc-cygwin" | ||
| * Change the runtime to be a superset of Cygwin in more places, e.g. make the CYGWIN env var work as a fallback if MSYS is not set. The goal is to make the Cygwin documentation mostly applicable to MSYS2 as well. |
There was a problem hiding this comment.
There are no env vars CYGWIN or MSYS set (at least not with my some month old MSYS2 install, neither in msys nor in mingw32 shells, nor in cygwin shell [most up to date]) either. Cygwin removes the OS variable, which is not done by any MSYS shells.
There was a problem hiding this comment.
It's not set by default, but it's used to configure cygwin behaviour: https://cygwin.com/cygwin-ug-net/using-cygwinenv.html (and is called MSYS in MSYS2, with some extra options)
What's OS?
|
Checked old MSYS/MinGW: does not set MINGW_CHOST/MSYSTEM_CARCH env vars. OSTYPE is shown as "msys" (but not seen in autotools config.guess returns i686-pc-mingw32 (MSYS/MINGW32), x86_64-pc-msys/x86_64-pc-mingw32/... (depending on the arch for MSYS2, not yet updated) and x86_64-pc-cygwin for cygwin |
OSTYPE is a bash thing and is defined at build time from what I know. |
No description provided.