Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 10 Jan 2001 17:00:05 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: make -mno-win32 the gcc default? Message-ID: <20010110170005.A5219@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010110163107.A4979@redhat.com> <4.3.1.2.20010110163516.021d82f8@pop.ma.ultranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <4.3.1.2.20010110163516.021d82f8@pop.ma.ultranet.com>; from lhall@rfk.com on Wed, Jan 10, 2001 at 04:36:41PM -0500 On Wed, Jan 10, 2001 at 04:36:41PM -0500, Larry Hall (RFK Partners, Inc) wrote: >At 04:31 PM 1/10/2001, Christopher Faylor wrote: >>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? > > >Yes. It fits with the stated goals of Cygwin. We can counter the outcry >with a nice FAQ so we at least will not have to repeat ourselves constantly. > >I'm in! You mean like this? Why am I getting errors from "windef.h"? Why am I getting errors saying simple things like "HANDLE" are undefined? Why can't I compile my Windows program with Cygwin 1.1.8? It worked fine with B19! Please send email to lhall@rfk.com and he'll explain everything. :-) cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple