Earnie skrev 2011-12-02 14:50:
> Peter Rosin wrote:
>> Fabian Greffrath skrev 2011-12-01 14:24:
>>> Am 01.12.2011 14:14, schrieb Fabian Greffrath:
>>>> Fine, that's exactly the stuff I was asking for: What's the exact
>>>> difference between MSYS and Cygwin apart from 's/cygwin/msys/g' in the
>>>> source code?
>>> Related question: On the mingw.org page I learn that MSYS is "a
>>> light-weight fork of Cygwin-1.3".
>>> How is "light-weight" defined if MSYS is more or less a renamed code
>>> copy of Cygwin with some specific changes?
>> MSYS does not fiddle with the process error mode (SetErrorMode) in the
>> same way Cygwin does, which means that you get popup dialogs when you
>> are trying to run programs that are missing DLLs etc (instead of a
>> more subtle non-zero exit status, only). But I don't know if that is
>> an MSYS feature to keep when doing a new fork?
> Are you comparing apples to oranges?
Certainly, because MSYS != Cygwin, and I also said that I didn't know
if that is an MSYS feature that it is desirable to keep so I thought
that was obvious.
> I.E. is your comparison of what
> Cygwin does based on the 1.3.3 version of Cygwin or is it based on what
> is delivered today as Cygwin? I don't believe this has any relevance to
> changes made to Cygwin for MSYS.
I have no knowledge of how Cygwin 1.3.3 behaved, I'm just stating a
current difference that I know about. I also think the popup will
not show up when MSYS runs another MSYS process, i.e. only when
running a "pure" win32 process (Cygwin will never popup error mode
induced dialogs), so it seems like a quite deliberate feature. The
feature is also in the win32-friendly category, which makes it more
likely to have an MSYS origin than a Cygwin origin. But again, I
don't know the origin of the feature.