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
Date: Fri, 26 Mar 2004 09:55:52 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin under Wine?
Message-ID: <20040326085552.GE17229@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OF5AB740AB DOT 55B11539-ON85256E63 DOT 0002D206-85256E63 DOT 000319EA AT us DOT ibm DOT com> <20040326025635 DOT GB17415 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040326025635.GB17415@redhat.com>
User-Agent: Mutt/1.4.2i

On Mar 25 21:56, Christopher Faylor wrote:
> 3) As Larry noted, you could use a cross-compiler.  I know that you maintain
>    that you would do testing under Wine but it seems rather foolhardy to
>    do all of your testing on an emaulator rather than a real Windows system.
>    I don't think your customers would be pleased if Wine somehow masked a
>    problem that only manifested on, say, Windows Server 2003.

Consequentielly, testing should not be done on Wine, but on something
like Bochs or VMware, if you're trying to avoid a real machine.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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