From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 0/2] Support for ccache
Date: Thu, 28 Oct 2021 19:19:49 +0300 [thread overview]
Message-ID: <4310624.niJfEyVGOH@hp> (raw)
In-Reply-To: <a5fb1b50-1f14-22c9-d081-301f1c70969a@siemens.com>
In mail from четверг, 28 октября 2021 г. 18:41:05 +03 user Jan Kiszka wrote:
> On 29.09.21 11:58, Uladzimir Bely wrote:
> > Changes since v1:
> > - Simplified used variables
> > - Rebased on latest `next`
> >
> > Some custom user packages built from sources may be written in C/C++.
> > Using ccache will help decrease build time in case they are rebuilt.
> >
> > For example, building `mc:stm32mp15x-buster:linux-mainline` during the
> > test took 28 minutes at second build with ccache enabled in comparison
> > with 115 minutes of first build.
> >
> > Uladzimir Bely (2):
> > meta: Support for ccache for custom packages in buildchroot
> > doc: Add section about ccache usage
> >
> > doc/user_manual.md | 17 ++++++++++++++
> > meta-isar/conf/local.conf.sample | 5 ++++
> > meta/classes/buildchroot.bbclass | 6 +++++
> > meta/classes/ccache.bbclass | 23 +++++++++++++++++++
> > meta/classes/dpkg.bbclass | 3 ++-
> > .../buildchroot/buildchroot.inc | 1 +
> > .../buildchroot/files/build.sh | 6 +++++
> > .../buildchroot/files/common.sh | 1 +
> > 8 files changed, 61 insertions(+), 1 deletion(-)
> > create mode 100644 meta/classes/ccache.bbclass
>
> What's the status here? I think we still wanted to simplify/unify the
> UI, aligning it to ISAR_CROSS_COMPILE.
>
> Jan
The new patchset is prepared, but a bit stucked at internal review.
In short, changes in it are the following:
- USE_CCACHE="1" in `local.conf` is used in to enable the feature in general.
- USE_CCACHE="0" can be set in the recipe to avoid caching even if it's
enabled in general
- ccache.bbclass was removed the main ccache-related variables were placed to
bitbake.conf.
--
Uladzimir Bely
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2021-10-28 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 9:58 Uladzimir Bely
2021-09-29 9:58 ` [PATCH v2 1/2] meta: Support for ccache for custom packages in buildchroot Uladzimir Bely
2021-09-29 9:58 ` [PATCH v2 2/2] doc: Add section about ccache usage Uladzimir Bely
2021-10-28 15:41 ` [PATCH v2 0/2] Support for ccache Jan Kiszka
2021-10-28 16:19 ` Uladzimir Bely [this message]
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=4310624.niJfEyVGOH@hp \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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