From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v4 0/3] Support of ccache
Date: Mon, 1 Nov 2021 11:09:38 +0100 [thread overview]
Message-ID: <20211101100941.23823-1-ubely@ilbers.de> (raw)
Changes since v3:
- Ci test for ccache excluded from `full` set of tests
Changes since v2:
- Using USE_CCACHE="1" to enable the feature instead of inheriting
- Removed ccache.bbclass, set required vars in bitbake.conf
- Addec CI test for ccache
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 to decrease build time in case they are rebuilt.
Some results measured:
`mc:stm32mp15x-buster:linux-mainline`: 115 min => 28 min;
`mc:de0-nano-soc-buster:isar-image-base`: 150 min => 81 min;
`mc:qemuamd64-bullseye:isar-image-base`: 17 min => 14 min.
Uladzimir Bely (3):
meta: Support for ccache for custom packages
doc: Add section about ccache usage
ci: Add test for ccache
doc/user_manual.md | 17 ++++++++++
meta-isar/conf/local.conf.sample | 5 +++
meta/classes/buildchroot.bbclass | 9 +++++
meta/classes/dpkg.bbclass | 2 +-
meta/conf/bitbake.conf | 5 +++
.../buildchroot/buildchroot.inc | 1 +
.../buildchroot/files/build.sh | 5 +++
.../buildchroot/files/common.sh | 1 +
testsuite/build_test/build_test.py | 11 +++++++
testsuite/build_test/cibase.py | 33 +++++++++++++++++++
10 files changed, 88 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2021-11-01 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 10:09 Uladzimir Bely [this message]
2021-11-01 10:09 ` [PATCH v4 1/3] meta: Support for ccache for custom packages Uladzimir Bely
2021-11-01 10:09 ` [PATCH v4 2/3] doc: Add section about ccache usage Uladzimir Bely
2021-11-01 10:09 ` [PATCH v4 3/3] ci: Add test for ccache Uladzimir Bely
2021-11-18 9:37 ` [PATCH v4 0/3] Support of ccache Anton Mikanovich
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=20211101100941.23823-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