Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Importance: Normal
Subject: Re: Using Cygwin with Windows 2000
To: cygwin AT sources DOT redhat DOT com
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF49736E92.3D22C18C-ON85256990.00676142@raleigh.ibm.com>
From: "Ed Bradford/Raleigh/IBM" <egb AT us DOT ibm DOT com>
Date: Tue, 7 Nov 2000 13:57:23 -0500
X-MIMETrack: Serialize by Router on D04NMS90/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at
 11/07/2000 01:57:25 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii

I am no expert on this issue, but, ...

I have ported one big thing and lots of little things. I have also built a
number of GNU utilities on Win2K. Gernally, if it
compiles with gcc on Linux, it will compile on CYGWIN gcc. Most of the
utilities I have compiled and run on CYGWIN have
already been configured to compile on CYGWIN (the configure shell script
knows about CYGWIN). You will have to deal
with  some incompatibilities (CR-LF versus LF, forward slash versus
backslash) even though CYGWIN minimizes these issues.
Also, if the program is performance intensive, you might want to write a
few test programs excercising those API's of most
interest to find out if the performance will be an issue.

XaoS (Real Time Fractal Zoomer) seems to perform quite acceptably compiled
with CYGWIN gcc. The resulting performance seems
indistinguishable from a Microsoft cl.exe compiled XaoS.exe (I have done
both). Finally, the same source code compiles and runs on
Linux. So unless your app is truely performance critical, CYGWIN might be
your best bet.

Ed Bradford

Your Windows 2000 Arborist
T/L 589-4410; Outside: 1-919-993-4410
egb AT us DOT ibm DOT com


"Larry Hall (RFK Partners Inc)" <lhall AT rfk DOT com>@sources.redhat.com on
11/07/2000 01:25:32 PM

Sent by:  cygwin-owner AT sources DOT redhat DOT com


To:   Marco Pettinella <Marco DOT Pettinella AT marconi DOT com>,
      cygwin AT sources DOT redhat DOT com
cc:   gianpaolo DOT borin AT prn DOT it, massimo DOT casali AT prn DOT it,
      antonio DOT tringali AT prn DOT it, Marcello Longo <Marcello DOT Longo AT marconi DOT com>
Subject:  Re: Using Cygwin with Windows 2000



At 03:10 AM 11/7/2000, Marco Pettinella wrote:


>Hi everybody.
>I'm going to start the porting of a Unix application to Windows NT/2000,
and I
>decided to use
>Cygwin. This porting will consist of two phases:
>1) Porting from Unix (POSIX) to NT (using cygwin)
>2) Porting to Windows 2000 (using ???)
>I've got a very simple question: does anybody have experienced Cygwin
>usage/development
>(DLL & commands/tools) in a Windows 2000 environment?
>If the answer is yes, does anybody know if the next stable release
(planned for
>early 2001) will
>support this operating system?
>
>Thanks in advance for your help.
>
>Marco Pettinella



I've been using Cygwin on W2K for 6 months now.  I know others on this list
have been using it for longer.  I have minimal experience in porting
packages
from UNIX to Windows platforms but I see no reason why Cygwin would address
this any worse (or perhaps better!;-)) for W2K than NT.  Is that your
question?



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com