All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Harald Nordgren <haraldnordgren@gmail.com>,
	Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Makefile: let ccache cache objects built with the precompiled header
Date: Wed, 28 Oct 2026 08:34:55 +0100	[thread overview]
Message-ID: <auGln4usFADtcUPB@pks.im> (raw)
In-Reply-To: <CALnO6CDpsQtAX0rHr9Cuot08K4j_6WMpiPOKA38sjDbWB-wj7A@mail.gmail.com>

On Tue, Oct 27, 2026 at 05:57:38PM -0400, D. Ben Knoble wrote:
> On Tue, Oct 27, 2026 at 4:00 PM Harald Nordgren
> <haraldnordgren@gmail.com> wrote:
> >
> > > And, what about Meson?
> >
> > I think it's not touched by this? My goal is just to speed up my local builds.
> 
> Yeah, it'd generally be nice to keep the 2 on par though ;)
> 
> I don't know enough about our pch infra, though, so I'll bow out from
> here. Just thought maybe we should make Meson do the same?

As Meson auto-detects ccache I'd think that stuff like this should
rather be handled in Meson itself. I e.g. found [1], which feels like
the right direction to me.

But if somebody wants to implement this in our instructions meanwhile I
won't complain.

Patrick

[1]: https://github.com/mesonbuild/meson/issues/14662

  reply	other threads:[~2026-10-28  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 12:40 [PATCH] Makefile: let ccache cache objects built with the precompiled header Harald Nordgren via GitGitGadget
2026-10-27 15:58 ` Ben Knoble
2026-10-27 20:00   ` Harald Nordgren
2026-10-27 21:57     ` D. Ben Knoble
2026-10-28  7:34       ` Patrick Steinhardt [this message]
2026-10-28  9:58         ` Harald Nordgren
2026-10-29  8:33 ` [PATCH v2] " Harald Nordgren via GitGitGadget

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=auGln4usFADtcUPB@pks.im \
    --to=ps@pks.im \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=haraldnordgren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.