From: NightStrike <nightstrike@gmail.com>
To: Junk Trash <junk.trash.36@hotmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Using CMake for building GCC
Date: Sun, 11 Sep 2022 12:27:58 -0400 [thread overview]
Message-ID: <CAF1jjLvE9oqzH7tkG-JYidJG5TDYoSdtkf91DS1Gr=vgGAmCtA@mail.gmail.com> (raw)
In-Reply-To: <SI2PR02MB6040ACF7367AFCFEDCD54C38AC459@SI2PR02MB6040.apcprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Sun, Sep 11, 2022, 10:30 Junk Trash via Gcc <gcc@gcc.gnu.org> 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
>
The high level premise of autotools is to make life harder for the build
system maintainer of a project and easier for a user. This makes sense on
several levels, including portability and familiarity. Cmake, on the other
hand, makes life somewhat easier for the build system maintainer (I
suppose) and harder for the user. This works for a pet project or something
without wide distribution, but I don't personally find it to be a good
design principle for usable and portable software.
Autotools isn't perfect (configure steps are slow, for instance), but it's
robust, reliable, portable, and trivial for an end user.
>
next prev parent reply other threads:[~2022-09-11 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 14:29 Junk Trash
2022-09-11 15:09 ` LIU Hao
2022-09-11 16:27 ` NightStrike [this message]
2022-09-12 8:07 ` Jose E. Marchesi
2022-09-13 6:30 ` Iru Cai
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='CAF1jjLvE9oqzH7tkG-JYidJG5TDYoSdtkf91DS1Gr=vgGAmCtA@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=junk.trash.36@hotmail.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).