This is the mail archive of the cygwin 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]
Other format: [Raw text]

Re: PING: Deprecation of -mno-cygwin.

Christopher Faylor <cgf-use-the-mailinglist-please <at>> writes:
> On Mon, Mar 23, 2009 at 02:22:03PM +0000, Greg Chicares wrote:
> >On 2009-03-23 14:00Z, Steve Thompson wrote:
> >> On Mon, 23 Mar 2009, Dave Korn wrote:
> >> 
> >>>  It's a bit of a kludge compared to having a real honest-to-god
> >>> cross-compiler.  It's never worked entirely right in terms of keeping
> >>> cygwin
> >>> and mingw headers and libs completely separate.
> >> 
> >> That's very interesting. I've been using -mno-cygwin for several years, 
> >> having done many many thousands of compiles and links using it, and I
> >> have 
> >> never had a problem with either headers or libraries! Is there a 
> >> recommended alternative?
> >
> >The recommended alternative is the forthcoming mingw cross-compiler.
> >
> >I think Yaakov's right to recommend a clean break with the past: ...
> >which would put all the confusion to rest.
> Big DITTO.  As Dave said, the option is already gone...

Moving to a better solution is great!  But isn't it customary to have some 
overlap period where the deprecated solution still works (but with ugly 
warnings) while the new solution is available?

I've used -mno-cygwin for many years, quite successfully, with no problems 
from headers or libraries.  I'm willing to upgrade all my Makefiles, but it 
would be nice to avoid a period where my Makefiles are broken and the new 
solution is not yet available.
Eric Backus

Unsubscribe info:
Problem reports:

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