From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dominik Michael Rauh <dmrauh@posteo.de>
Cc: anders.f.bjorklund@gmail.com, andrew.smirnov@gmail.com,
s.martin49@gmail.com, buildroot@buildroot.org,
fontaine.fabrice@gmail.com, thomas.de_schampheleire@nokia.com
Subject: Re: [Buildroot] [PATCH v3] package/ccache: bump version to 4.6.1
Date: Sun, 7 Aug 2022 14:39:36 +0200 [thread overview]
Message-ID: <20220807143936.3f3e0898@windsurf> (raw)
In-Reply-To: <20220807091341.10523-1-dmrauh@posteo.de>
On Sun, 7 Aug 2022 09:13:41 +0000
Dominik Michael Rauh <dmrauh@posteo.de> wrote:
> > Just curious, what are these doing?
>
> These two options remove the corresponding CMake CACHE entries that are set at
> the beginning of "package/pkg-cmake.mk", when BR2_CCACHE=y (please also see
> https://cmake.org/cmake/help/latest/prop_tgt/LANG_COMPILER_LAUNCHER.html). Thus
> Buildroot is not trying to compile ccache using ccache :)
OK, makes sense!
> > It's really a pity that we need to disable ccache support to build
> > host-cmake, because host-cmake is notoriously slow to build... But
> > obviously since ccache is now using cmake as its build system, I don't
> > really see a much better solution.
>
> Yes, the more external dependencies ccache gains, the less beneficial it may
> become. One could think about making ccache a "multi-stage build", where at
> first, it is only compiled with all of its essential dependencies and then at a
> later stage, all other dependencies are "added". But that's probably more
> trouble than it's worth and certainly out of the question for CMake.
A possible alternative we could explore is to no longer build ccache
ourselves and rely on ccache being provided by the host distribution.
Of course, raises the question of which ccache version is available on
the host, and how to tweak its configuration to match the needs of
Buildroot.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-07 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 13:29 [Buildroot] [PATCH 1/1] package/ccache: bump version to 4.6.1 Dominik Michael Rauh
2022-08-05 10:24 ` [Buildroot] [PATCH v2] " Dominik Michael Rauh
2022-08-05 13:13 ` [Buildroot] [PATCH v3] " Dominik Michael Rauh
2022-08-05 14:34 ` Thomas Petazzoni via buildroot
2022-08-07 9:13 ` Dominik Michael Rauh
2022-08-07 12:39 ` Thomas Petazzoni via buildroot [this message]
2022-08-07 17:55 ` Dominik Michael Rauh
2022-08-07 9:38 ` [Buildroot] [PATCH v4] " Dominik Michael Rauh
2023-01-08 22:37 ` Yann E. MORIN
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=20220807143936.3f3e0898@windsurf \
--to=buildroot@buildroot.org \
--cc=anders.f.bjorklund@gmail.com \
--cc=andrew.smirnov@gmail.com \
--cc=dmrauh@posteo.de \
--cc=fontaine.fabrice@gmail.com \
--cc=s.martin49@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.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