This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gcc 2.95.3-1 and -mwin32


----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin-apps@cygwin.com>
Sent: Sunday, March 18, 2001 10:07 AM
Subject: Re: gcc 2.95.3-1 and -mwin32


> On Sat, Mar 17, 2001 at 06:01:59PM -0500, Charles S. Wilson wrote:
> >Christopher Faylor wrote:
> >>
> >> I've got gcc 2.95.3-1 ready to go.  It seems to work ok.
> >
> >[snip]
> >
> >> So, unless someone has a strong objection, the default for gcc
2.95.3-1,
> >> gcc 3.0, and gcc 3.1 will be to include /usr/include/w32api.
> >
> >Q: Does that also mean that the default for gcc-2.95.3-1 on cygwin
will
> >be to #define WIN32 & WINDOWS in addition to merely including
> >/usr/include/w32api in the include path?  e.g. that -mwin32 is the
> >default now (again)?
>
> I wasn't planning on doing this, no.  I still think that Cygwin should
not
> define these unless asked.
>
> This does cause problems for some of the stuff in sources.redhat.com
but
> they are minor compared to the effort of adding -mwin32 everywhere
that
> it was needed.
>
> So, this is still different from gcc-2.95.2-1.
>
> cgf
>

Will -mwin32 still be present? I think it should if you do not define
WIN32.

Rob


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]