This is the mail archive of the
mailing list for the Cygwin project.
merging mingw and cygwin
- From: Edward Peschko <esp5 at pge dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 10 Oct 2003 17:16:48 -0700
- Subject: merging mingw and cygwin
I've been playing around with mingw and cygwin, and was wondering why these were separate
projects? I've been trying to get a unix API moved over to windows; I want a Unix
environment, but at the same time want to be able to make Win32 native binaries,
*without* the need of the cygwin dlls.
So - I've been trying various things:
4) mks toolkit
all of which are unsatisfactory in some way or another. #3 and #4 in particular are
proprietary; and #3 and #4 both have less support in gnu tools than I care for. #3 looks
nice, but furthermore doesn't seem to be supported in at&t anymore..
However, #1 and #2 are a puzzle: why are they two separate projects? Its terribly
confusing; both have the same executable files created (ln and rm, for example) so
its hard to use one with the other; and its got to be a maintenance nightmare to
support separate patches for mingw and separate patches for cygwin.
So - why aren't the two merged? Why isn't there a 'mingw' mode for cygwin, where
the ability to use the cygwin*.dll is turned off, and mingw executables can be compiled
under cygwin tools? And where constructs like using shortcuts for symlinks are turned
off, to make projects more win32 friendly...
I'd think that this would be easier in the long run. If the two projects were merged..
But then again, who am I to make such a decision.. ;-)
Interested in any comments.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html