public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gcc@gcc.gnu.org, mingw-w64-public@lists.sourceforge.net
Subject: Re: gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library
Date: Sun, 20 Nov 2022 16:04:11 +0100	[thread overview]
Message-ID: <20221120150411.yimchs4ic3xtvny3@pali> (raw)
In-Reply-To: <83cz9h65wc.fsf@gnu.org>

On Sunday 20 November 2022 16:45:55 Eli Zaretskii wrote:
> > Date: Sun, 20 Nov 2022 13:53:48 +0100
> > From: Pali Rohár via Gcc <gcc@gcc.gnu.org>
> > 
> > Hello! I would like to propose a new parameter for gcc: -mcrtdll= to
> > allow specifying against which Windows C Runtime library should be
> > binary linked. On Windows there are more crt libraries and currently gcc
> > links to libmsvcrt.a which is in most cases symlink to libmsvcrt-os.a
> > (but can be changed, e.g. during mingw-w64 building). mingw-w64 project
> > already builds import .a library for every crt dll library (from the old
> > crtdll.dll up to the new ucrtbase.dll), so it is ready for usage. Simple
> > patch for gcc which implements -mcrtdll parameter is below. Note that on
> > internet are other very similar patches for -mcrtdll= parameters and
> > some are parts of custom mingw32 / mingw-w64 gcc builds. What do you
> > think? Could gcc have "official" support for -mcrtdll= parameter?
> 
> Linking a program against a specific runtime means the produced binary will
> not run on Windows systems older than the one where it was linked.  Why is
> such a limitation a good idea, may I ask?

It will run also on older Windows system if you install redistributable
runtime library. Which in most cases is already installed because other
programs use it.

And why you want a new version? Because of better C99/C11 support which
is in ucrtbase.dll

Note that with this option, you can also choose older version than the
default one (WinXP msvcrt.dll). So e.g. you can choose msvcrt20.dll or
crtdll.dll for older Windows version.

  reply	other threads:[~2022-11-20 15:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 12:53 Pali Rohár
2022-11-20 13:36 ` [Mingw-w64-public] " LIU Hao
2022-11-20 15:06   ` Pali Rohár
2022-11-21  5:21     ` LIU Hao
2022-11-26 19:09       ` Pali Rohár
2022-11-27  1:06         ` sotrdg sotrdg
2022-11-20 14:45 ` Eli Zaretskii
2022-11-20 15:04   ` Pali Rohár [this message]
2022-11-20 15:23     ` Eli Zaretskii
2022-11-20 15:44       ` Pali Rohár
2022-11-20 15:58         ` Eli Zaretskii
2022-11-20 16:19           ` [Mingw-w64-public] " ralph engels
2022-11-20 16:20           ` Matthew Brett
2022-11-20 21:22 ` Martin Storsjö
2022-12-04 12:16 ` Pali Rohár
2022-12-04 12:48   ` LIU Hao
2023-04-21 16:23     ` Pali Rohár
2023-05-06 10:45       ` Pali Rohár
2023-05-08  3:44         ` LIU Hao

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=20221120150411.yimchs4ic3xtvny3@pali \
    --to=pali.rohar@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mingw-w64-public@lists.sourceforge.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).