public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/2] Support for ccache
Date: Wed, 29 Sep 2021 11:58:08 +0200	[thread overview]
Message-ID: <20210929095810.3228-1-ubely@ilbers.de> (raw)

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

-- 
2.20.1


             reply	other threads:[~2021-09-29  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  9:58 Uladzimir Bely [this message]
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

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=20210929095810.3228-1-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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