This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Does -mno-cygwin sometimes have no effect?
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Subject: Does -mno-cygwin sometimes have no effect?
- From: Deneb Meketa <dmeketa at macromedia dot com>
- Date: Wed, 11 Jul 2001 16:56:37 -0700
It seems to me that when I use the -mno-cygwin option to gcc,
this has the intended effect (no dependency on cygwin1.dll)
most of the time, but in situations where certain additional
cygwin libs are needed (in my case, cygintl.dll), -mno-cygwin
doesn't do anything; the output exe always requires cygwin
libs.
Is this correct? This would make sense if there is no Windows
equivalent to something like cygintl.dll. However, if this is
in fact the case, I would love a warning from gcc indicating
that honoring -mno-cygwin will not be possible.
Many thanks
d.
--
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/