Linked by Thom Holwerda on Wed 23rd Dec 2009 23:49 UTC, submitted by diegocg
Linux After two long years since the last release, Cygwin 1.7 (a Linux-like environment that runs on Windows systems) has been released. Among many other improvement, this release adds support for Windows 7 and Server 2008R2.
Permalink for comment 400863
To read all comments associated with this story, please click here.
mingw/cygwin ... 2010 and beyond?
by kad77 on Thu 24th Dec 2009 01:11 UTC
kad77
Member since:
2007-03-20

What are the chances of MinGW and Cygwin ever merging?

While I mostly (95% for years) use MinGW for cross-porting to windows, because I like the "true" native binary without external dependencies; MSYS/MinGW seems to be a herculean effort mostly on the backs of very few people. Getting DirectX and other headers/libs is very DIY/scattered...

But *everything* works, eventually. I commonly can get cygwin ports, or just unported linux apps to compile with a few hours work (CLI, of course). But porting SDL apps is trivial.

At this point, "unofficial" gcc mingw compilers are coming out many months ahead of regular official releases, and Cygwin releases are years behind mingw (look at the gcc 4.x series).

I know MSYS/MinGW has somewhat of a different philosophy (I welcome different takes on this) than the Cygwin project, but it seems that so few talented people are able to do this level of largely non-compensated work, that it would make the most sense to pool their efforts.

In my mind it seems to be an OpenBSD vs FreeBSD type situation (to use a rough O/S analogy)...

Can anyone else share there insights/experiences with Cygwin vs MinGW, and where we can expect GCC on windows to go in the future?

I would love to have more insight into the development differences, and whether I should finally switch away from non-official MinGW builds + CodeBlocks to the larger and slower moving (?, imo) Cygwin project??

Thanks for this post!

Edited 2009-12-24 01:14 UTC

Reply Score: 3