public inbox for
 help / color / mirror / Atom feed
From: Iru Cai <>
Subject: Re: Using CMake for building GCC
Date: Tue, 13 Sep 2022 14:30:25 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

In my opinion, the advantage of autotools is that it can generate a 
configure script that can be shipped with the source tarball, then any 
one with the source can run the configure script when the system has a 
POSIX shell and tools. If using CMake, meson, xmake, etc. the user will 
first need to install the build tool to build the source.

I still hope to have one such build tool which can generate a configure 
script, and have some better properties than autotools:

- implemented in a sane language (I don't like Perl)

- generate a single configure script for the whole project instead of 
running configure on subprojects when running make

- support building with ninja

If CMake, meson, xmake or some other build system support generating a 
POSIX shell configure script, I think it would be fine to use it to 
replace autotools.

On 2022/9/11 22:29, Junk Trash via Gcc wrote:
> Hi,
> I want to get the opinions of GCC developers regarding adding CMake as a build system for GCC. Is it something you would like, something you are neutral about, or something you are strongly against?
> Thanks for your valuable feedback!
> Regards,
> JT

      parent reply	other threads:[~2022-09-13  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-09-11 15:09 ` LIU Hao
     [not found] ` <>
2022-09-12  8:07   ` Jose E. Marchesi
2022-09-13  6:30 ` Iru Cai [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).