Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Paul G." Organization: NewDawn Productions To: cygwin AT cygwin DOT com Date: Sat, 11 Oct 2003 21:20:17 -0700 MIME-Version: 1.0 Subject: Re: merging mingw and cygwin Reply-to: pgarceau AT attbi DOT com Message-ID: <3F887411.3666.1A02EE3@localhost> In-reply-to: <20031012020146.GA11314@mdssirds.comp.pge.com> References: <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20031011194820 DOT 02edbe98 AT 127 DOT 0 DOT 0 DOT 1> Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Got an error from qmail the last time I sent this. Trying again...please, forgive any duplication. On 11 Oct 2003 at 19:01, Edward Peschko wrote: 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. Mingw requires a different runtime than does Cygwin. Mingw is short for Minimalist-Gnu for Windows. It's function, at least in my mind, is to act as a "native" gcc/g++ build environment which does not rely on either posix or any unix-like support. Afaik, whenever a new Mingw distribution comes out, Cygwin gets a copy of that distribution, probably minus the Mingw specific binaries and utilities. Paul G. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/