public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Up-to-date info on '-mno-cygwin' vs. Mingw32
Date: Fri, 31 Aug 2001 07:53:00 -0000	[thread overview]
Message-ID: <20010831105340.A22420@redhat.com> (raw)
In-Reply-To: <000501c13210$54396e40$6401a8c0@atl.mediaone.net>

On Fri, Aug 31, 2001 at 07:30:16AM -0400, David Carter wrote:
>Jesper Eskilson wrote:
>> According to the FAQ, support for the -mno-cygwin flag "has been weak
>>and flaky, [...] and maintenance of the option has *not* been a
>>priority in development", 
>
>I would tend to agree with this.

I'm not sure what FAQ is referring to this but it is rather
disappointing to hear that all of the work I've put into getting this
right is considered "weak" and "flaky".

For instance, I recently added code to binutils to allow isolation of
the various required libraries so that -mno-cygwin can only use mingw
and w32api libraries.

The only lack that I'm currently aware of is C++.  I have asked for
someone to send me a drop in libstdc++.a library for the current cygwin
version of gcc.  I don't think that anyone has taken me up on that
offer.

>>and the FAQ recommends that one uses a
>>separate MingW compiler set. Is this accurate?
>
>Here's what I recommend:
>- use the cygwin tools, passing -mno-cygwin to the compiler (& linker? I
>do it to be sure, but not sure if it's required)
>- use the mingw headers & libraries -- download them from mingw, and
>copy or symlink them into your cygwin /usr/include/mingw and
>/usr/lib/mingw directory trees. This is absolutely required if you're
>doing anything with c++ that you want to run on win32 without the
>cygwin1.dll

Hopefully most of the mingw headers and libraries are the same as
the ones in the current cygwin release.  If they aren't, they should
be updated.

Basically, I have been saying that -mno-cygwin is not something that I
enjoy working on since it is rather diametrically opposed to my main
cygwin activities.  However, I *have* spent a lot of time trying to
get it right, mainly because I don't like to release code that only
half works.

One of the reasons that I haven't released gcc 3.0* is that I would have
to patch the preprocessor to handle some of my "hacks" and the
preprocessor has changed drastically since 2.95.*.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2001-08-31  7:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30  4:25 Jesper Eskilson
2001-08-30  6:33 ` Larry Hall (RFK Partners, Inc)
2001-08-30  8:27   ` Gerald W. Shapiro
2001-08-30 23:52   ` Jesper Eskilson
2001-08-31  4:29     ` David Carter
2001-08-31  7:36       ` Jesper Eskilson
2001-08-31  7:53       ` Christopher Faylor [this message]
2001-08-31 14:53       ` James Youngman
2001-09-01 19:08     ` Paul G.
2001-09-08  8:01       ` David Starks-Browning
2001-08-30 17:32 ` Paul G.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010831105340.A22420@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).