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
Message-Id: <6.0.1.1.0.20040325201031.02854fd8@pop.rcn.com>
X-Sender: lhall AT pop DOT rcn DOT com (Unverified)
Date: Thu, 25 Mar 2004 20:19:15 -0500
To: Thomas L Roche <tlroche AT us DOT ibm DOT com>, cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Cygwin under Wine?
In-Reply-To: <OF9F508893.6F941F4F-ON85256E63.0004A326-85256E63.000566F4@ us.ibm.com>
References: <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040325194138 DOT 028547a0 AT pop DOT rcn DOT com> <OF9F508893 DOT 6F941F4F-ON85256E63 DOT 0004A326-85256E63 DOT 000566F4 AT us DOT ibm DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 07:59 PM 3/25/2004, you wrote:
>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.


So are you saying that it's not a requirement that your build environment
running under Wine be able to run smoke/unit/function tests but it would
be for a cross-compiler environment would?  Yikes!  OK, maybe I 
misunderstood what you're saying with the above but if that's 
the case, it seems to me that the bigger concern should be "will the
software built under Wine run under Wine"?  Unless you know that's the case,
you're putting the cart before the horse.  And, as I type this, I have
the strangest feeling of deja-vu, like this is exactly the same comment
that was made the last time this subject came up. ;-)



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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