Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
In-Reply-To: <6.0.1.1.0.20040325194138.028547a0@pop.rcn.com>
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Subject: Re: Cygwin under Wine?
From: Thomas L Roche <tlroche AT us DOT ibm DOT com>
Message-ID: <OF9F508893.6F941F4F-ON85256E63.0004A326-85256E63.000566F4@us.ibm.com>
Date: Thu, 25 Mar 2004 19:59:00 -0500
Content-Type: text/plain; charset="US-ASCII"

At 07:33 PM 3/25/2004, Tom Roche wrote:
> While sounding out Cygwin users in my organization, I got the
> comment:

> > If Cygwin would run under Wine, I'd be a very happy person, we
> > wouldn't need real Windows machines for builds, and we could
> > consign all our Windows build machines, their ITSC compliance, and
> > the continual stream of updates and security fixes to the deepest
> > pits of hell.

Larry Hall 03/25/2004 07:45:39 PM:
> I'm not sure I see the logic in the comment from which the question
> stems. If the goal is to avoid using Windows platforms for builds,
> why isn't a cross-compiler targeting Windows enough?

For one thing, in these modern times, building usually also involves
some smoke-, unit- or function-test (i.e. "build verification test").

As far as the administrative desirability of running an emulator vs
running native: this may be an organizational peculiarity, but IIRC
the same requirements don't apply.


--
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/