Message-Id: <200005251558.LAA00290@delorie.com>
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: "Parker, Ron" <rdparker AT butlermfg DOT com>
To: Cosmin Truta <cosmin AT cs DOT toronto DOT edu>,
        Charles Wilson
	 <cwilson AT ece DOT gatech DOT edu>
Cc: Jason Tishler <Jason DOT Tishler AT dothill DOT com>, cygwin AT sourceware DOT cygnus DOT com
Subject: RE: CygUtils Version of zip (and Symlinks)
Date: Thu, 25 May 2000 10:56:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFC661.EE7398C6"

------_=_NextPart_000_01BFC661.EE7398C6
Content-Type: text/plain;
	charset="windows-1252"

> > When you get right down to it, cygwin is NOT windows. It 
> does everything
> > it can to make windows look like Unix, so that apps can run 
> *as if they
> > were on unix* with little or no changes. So, by that logic,
> > cygwin-zip/unzip =should= be built as unix-ish apps, not windows-ish
> > ones.
> 
> Maybe you are right.
> I personally look at gcc as a free alternative for a good 
> Win32 compiler,
> but I agree that cygwin is a "Unix on Win" and maybe most of 
> the people
> look at it that way.

ISTM that the right behavior would be for cygwin to build a UNIX-ish (un)zip
and for mingw to build a Windows style program.  As already pointed out
cygwin should be thought of as "Unix on Win" and IMO mingw should be thought
of as "as a free alternative for a good Win32 compiler". 

I realize that cygwin and mingw are both supported by the same compiler, but
supplying -mno-cygwin causes gcc to switch from cygwin to mingw behavior and
__MINGW32__ becomes defined.

This may be more a question for cygwin-developers, but I hate crossposts and
know most readers of that list at least review this one.  So, wouldn't it be
appropriate when compiling without -mno-cygwin for the specs file to define
"unix", "UNIX" and similar "standard" defines?  They seem to be checked for
in newlib, zlib, X11, and many other sources?

Yes I know I can make this change in my local sources, but I prefer to work
with standard sources and now seemed a good time to bring it up.  I have
been wondering about it for some time.


------_=_NextPart_000_01BFC661.EE7398C6
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
------_=_NextPart_000_01BFC661.EE7398C6--