Mail Archives: cygwin/2000/10/18/11:05:29
On Thursday 19 Oct 00, Fergus Henderson writes:
> On 16-Oct-2000, Earnie Boyd <earnie_boyd AT yahoo DOT com> wrote:
> > --- Chris Faylor <cgf AT cygnus DOT com> wrote:
> > > On Mon, Oct 16, 2000 at 09:51:11AM -0700, Earnie Boyd wrote:
> > > >
> > > >The -mno-cygwin switch of the Cygwin product is not considered MinGW by
> > > >the MinGW development team. MinGW has it's own set of GCC/binutils
> > > >tools. We are currently in the process of preparing a more upto date
> > > >package.
>
> OK, I have some follow-up questions:
>
> - Is there much difference between the two?
I would also like some clarification about this, for the FAQ. It
currently says:
Q: How do I compile a Win32 executable that doesn't use Cygwin?
A: The -mno-cygwin flag to gcc makes gcc link against standard
Microsoft DLLs instead of Cygwin. This is desirable for native
Windows programs that don't need a UNIX emulation layer.
This is not to be confused with 'MinGW' (Minimalist GNU for
Windows), which is a completely separate effort. That
project's home page is http://www.mingw.org/index.shtml.
On the other hand, I've read on this list that Cygwin contains
"mingw", and this is what you get with -mno-cygwin. (Or rather, *a
version* of it, perhaps this is the distinction?)
If someone could contribute a useful, coherent entry, I would add it
to the FAQ. I am blissfully ignorant of MinGW and -mno-cygwin.
Thanks,
David
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -