From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: NightStrike via Gcc <gcc@gcc.gnu.org>
Cc: Junk Trash <junk.trash.36@hotmail.com>,
NightStrike <nightstrike@gmail.com>
Subject: Re: Using CMake for building GCC
Date: Mon, 12 Sep 2022 10:07:53 +0200 [thread overview]
Message-ID: <87sfkxdnhi.fsf@oracle.com> (raw)
In-Reply-To: <CAF1jjLvE9oqzH7tkG-JYidJG5TDYoSdtkf91DS1Gr=vgGAmCtA@mail.gmail.com> (NightStrike via Gcc's message of "Sun, 11 Sep 2022 12:27:58 -0400")
> 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.
Very well said. Distributed source tarballs are a blessing for both
distros and users.
Often people suggesting replacing autotools with CMake do so under the
assumption these two programs do the same thing: they don't.
I would very strongly oppose using CMake for building any program I
contribute to, and I would certainly never use it in any program I
maintain myself.
next prev parent reply other threads:[~2022-09-12 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SI2PR02MB6040ACF7367AFCFEDCD54C38AC459@SI2PR02MB6040.apcprd02.prod.outlook.com>
2022-09-11 15:09 ` LIU Hao
[not found] ` <CAF1jjLvE9oqzH7tkG-JYidJG5TDYoSdtkf91DS1Gr=vgGAmCtA@mail.gmail.com>
2022-09-12 8:07 ` Jose E. Marchesi [this message]
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=87sfkxdnhi.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gcc@gcc.gnu.org \
--cc=junk.trash.36@hotmail.com \
--cc=nightstrike@gmail.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).