From: LIU Hao <lh_mouse@126.com>
To: Junk Trash <junk.trash.36@hotmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Using CMake for building GCC
Date: Sun, 11 Sep 2022 23:09:41 +0800 [thread overview]
Message-ID: <819a41c8-d4a2-f142-75eb-aed75fc6f71e@126.com> (raw)
In-Reply-To: <SI2PR02MB6040ACF7367AFCFEDCD54C38AC459@SI2PR02MB6040.apcprd02.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 385 bytes --]
在 2022-09-11 22:29, Junk Trash via Gcc 写道:
> 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!
>
>
https://twdev.blog/2021/08/cmake/
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-09-11 15:09 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 [this message]
2022-09-11 16:27 ` NightStrike
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=819a41c8-d4a2-f142-75eb-aed75fc6f71e@126.com \
--to=lh_mouse@126.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).