Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Wed, 10 Jan 2001 16:31:07 -0500
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: make -mno-win32 the gcc default?
Message-ID: <20010110163107.A4979@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i

So, what does everyone think about making -mno-win32 the default for Cygwin?

This would mean that WIN32 variables would not be defined by gcc by default.
It would require a -mwin32 switch for these to be activated.

Earnie has been proposing this and I sort of like the idea but dread the
potential hue and cry that could result.

So, is the hue and cry from the lack of WIN32 counterbalanced by potentially
easier UNIX porting?

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple