From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Don Kuenz <mail@crcomp.net>
Subject: Re: Does i686-w64-mingw32-gcc now use -mno-cygwin by default?
Date: Wed, 18 Jan 2023 11:42:50 -0700 [thread overview]
Message-ID: <96c22419-377c-7d26-bb29-ef81564f4490@Shaw.ca> (raw)
In-Reply-To: <507e7dfc987741cc10f1b21540fc02a4@crcomp.net>
On 2023-01-17 15:25, Don Kuenz via Cygwin wrote:
> Greetings,
>
> Back in the day i686-pc-mingw32-gcc used the -mno-cygwin flag to break
> the implicit link to cygwin1.dll. It enabled developers to release a
> standalone binary. In other words, cygwin1.dll did not have to be
> installed on the user's PC in order for a standalone binary to run.
>
> i686-pc-mingw32-gcc is no longer available. And i686-w64-mingw32-gcc now
> seems to create standalone binaries by default. The binaries run on a
> target PC without cygwin1.dll installed.
>
> Can someone confirm i686-w64-mingw32-gcc in its default mode now creates
> standalone binaries?
The -no-/-cygwin options were removed in 2010 except for:
$ info gcc Invoking Option
/Windows
invoke.texi/Option Summary/x86 Windows Options at:
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/invoke.texi#l1454
1453 @emph{x86 Windows Options}
1454 @gccoptlist{-mconsole -mcygwin -mno-cygwin -mdll @gol
1455 -mnop-fun-dllimport -mthread @gol
1456 -municode -mwin32 -mwindows -fno-set-stack-executable}
from which the man gcc Windows options are generated with texi2pod and pod2man.
The mingw toolchains are used to build native Windows objects and files.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-01-18 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 22:25 Don Kuenz
2023-01-18 18:42 ` Brian Inglis [this message]
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=96c22419-377c-7d26-bb29-ef81564f4490@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.com \
--cc=mail@crcomp.net \
/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).