From: Don Kuenz <mail@crcomp.net>
To: cygwin@cygwin.com
Subject: Does i686-w64-mingw32-gcc now use -mno-cygwin by default?
Date: Tue, 17 Jan 2023 16:25:55 -0600 [thread overview]
Message-ID: <507e7dfc987741cc10f1b21540fc02a4@crcomp.net> (raw)
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?
Thank you in advance.
Danke,
--
Don, KB7RPU, https://www.qsl.net/kb7rpu
There was a young lady named Bright Whose speed was far faster than
light;
She set out one day In a relative way And returned on the previous
night.
--
Don Kuenz
307 266 3327 x1
next reply other threads:[~2023-01-17 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 22:25 Don Kuenz [this message]
2023-01-18 18:42 ` Brian Inglis
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=507e7dfc987741cc10f1b21540fc02a4@crcomp.net \
--to=mail@crcomp.net \
--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).