From: vspefs <vspefs@protonmail.com>
To: Ben Boeckel <ben.boeckel@kitware.com>
Cc: Nathaniel Shead <nathanieloshead@gmail.com>,
"Jose E. Marchesi" <jose.marchesi@oracle.com>,
gcc <gcc@gcc.gnu.org>, joergboe <joergboe@snafu.de>
Subject: Re: Generation of Make Dependencies for C++ Modules
Date: Tue, 30 Dec 2025 13:47:32 +0000 [thread overview]
Message-ID: <5jmZaIVhB-XvY4gihAHGvrsXu9_IlvLT0lxmtMBf7GFSOOGtlqxk5kQQXWNeoGgBG4Z4OHxcQgcD9gK7TQ_grc9KL7A336rTDLdE3Ck8QTU=@protonmail.com> (raw)
In-Reply-To: <aVKoshGL79iKsEsE@rotor>
> Note that I'd like to avoid yet another format because I doubt autotools
> wants its module support to be "GCC only". I know LLVM-as-frontend is
> eating the lunch of proprietary compilers, and P1689R5 is already there,
> so that seems like an easy win to me.
>
> I guess the main hurdle is either porting some JSON parser to an
> automake-compatible language or growing a dependency on something like
> `jq`.
True. But I mean GCC and Clang consume CMI in very different ways so I guess
even if the dependency scanning and collating logic can be shared, there has
to be some "special treatment". Or GCC augments its current built-in module
mapper to support `-fmodule-file` behavior so that "special treatment" is
really minimum. Though far as I remember CMake passes a `.modmap` file as the
module mapper flag value and it works?
By the way, Automake is written in Perl. Parsing JSON in Perl is like one of
the easiest things on Earth so I think everyone should be happy about it.
> This was added recently:
>
> https://github.com/cps-org/cps/pull/95
> CPS has a similar concept to CMake's compile option usage requirements,
> so projects requiring specific flags can be propagated that way.
>
> Note that CMake because re-builds BMIs at the consuming side, compatible
> flags is down to the same ABI concerns we've always had with header and
> library artifact mismatches that have always existed.
I do have some opinions but I’ll talk about it in the CPS community.
next prev parent reply other threads:[~2025-12-30 13:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 18:11 joergboe
2025-12-23 16:23 ` Ben Boeckel
2025-12-25 18:28 ` joergboe
2025-12-26 3:16 ` Ben Boeckel
2025-12-27 5:50 ` vspefs
2025-12-27 11:24 ` Jose E. Marchesi
2025-12-27 12:01 ` Arsen Arsenović
2025-12-28 4:31 ` vspefs
2025-12-28 14:30 ` Jose E. Marchesi
2025-12-28 21:50 ` Nathaniel Shead
2025-12-29 0:03 ` vspefs
2025-12-29 2:31 ` Ben Boeckel
2025-12-29 6:12 ` vspefs
2025-12-29 16:13 ` Ben Boeckel
2025-12-30 13:47 ` vspefs [this message]
2025-12-30 16:19 ` Ben Boeckel
2025-12-30 16:54 ` Arsen Arsenović
2025-12-29 2:50 ` Ben Boeckel
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='5jmZaIVhB-XvY4gihAHGvrsXu9_IlvLT0lxmtMBf7GFSOOGtlqxk5kQQXWNeoGgBG4Z4OHxcQgcD9gK7TQ_grc9KL7A336rTDLdE3Ck8QTU=@protonmail.com' \
--to=vspefs@protonmail.com \
--cc=ben.boeckel@kitware.com \
--cc=gcc@gcc.gnu.org \
--cc=joergboe@snafu.de \
--cc=jose.marchesi@oracle.com \
--cc=nathanieloshead@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).