On Mon, Sep 2, 2013 at 6:44 PM, Ray Donnelly <[email protected]>wrote:
> Also, I already answered that question.
>
> "MSYS2 is basically Cygwin without the posix-purity stuff going and
> instead a laser sharp focus on interoperability between MSYS2 tools
> and Windows tools. It is "still Windows" but it uses it's own GCC that
> links to (and creates software that links to) msys-2.0.dll that
> provides a more posix-like set of system libraries and environment.
>
> A regular Windows toolchain would not be the same."
>
> .. could you do us all a huge favour and actually bother to read the
> replies people write to you, or just use Google?
>
I actually read that reply. That is what confused me. I guess I didn't
understand the term "POSIX-purity stuff". I had understood your answer to
mean that MSYS provides posixy tools and libraries and a shell so that
things like autoconf and various make scripts and #includes will work, but
this is all just for compile time and in the end the compiled programs are
Windowsy, while cygwin lets them compile and run as i on a posix system,
with the .dll supplying the missing parts at runtime.
Then another answer here said that MSYS also had this .dll issue, and that
was what confused me.
--
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
