* Does i686-w64-mingw32-gcc now use -mno-cygwin by default?
@ 2023-01-17 22:25 Don Kuenz
2023-01-18 18:42 ` Brian Inglis
0 siblings, 1 reply; 2+ messages in thread
From: Don Kuenz @ 2023-01-17 22:25 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Does i686-w64-mingw32-gcc now use -mno-cygwin by default?
2023-01-17 22:25 Does i686-w64-mingw32-gcc now use -mno-cygwin by default? Don Kuenz
@ 2023-01-18 18:42 ` Brian Inglis
0 siblings, 0 replies; 2+ messages in thread
From: Brian Inglis @ 2023-01-18 18:42 UTC (permalink / raw)
To: cygwin; +Cc: Don Kuenz
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-01-18 18:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-17 22:25 Does i686-w64-mingw32-gcc now use -mno-cygwin by default? Don Kuenz
2023-01-18 18:42 ` Brian Inglis
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).