From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] scripts/ci: enable use of cached base repository for fast build
Date: Thu, 29 Nov 2018 08:58:45 +0100 [thread overview]
Message-ID: <9759704e-9c29-36ba-cbdb-1a252692d34a@siemens.com> (raw)
In-Reply-To: <20181129071918.29263-1-mosipov@ilbers.de>
On 29.11.18 08:19, Maxim Yu. Osipov wrote:
> Signed-off-by: Maxim Yu. Osipov <mosipovd@ilbers.de>
> ---
> scripts/ci_build.sh | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> index 059df21..20b77b7 100755
> --- a/scripts/ci_build.sh
> +++ b/scripts/ci_build.sh
> @@ -86,7 +86,14 @@ fi
> if [ -n "$FAST_BUILD" ]; then
> # Start build for the reduced set of configurations
> # Enforce cross-compilation to speed up the build
> + # Enable use of cached base repository
> sed -i -e 's/ISAR_CROSS_COMPILE ?= "0"/ISAR_CROSS_COMPILE ?= "1"/g' conf/local.conf
> + bitbake $BB_ARGS -c cache_base_repo \
> + multiconfig:qemuarm-stretch:isar-image-base \
> + multiconfig:qemuarm64-stretch:isar-image-base \
> + multiconfig:qemuamd64-stretch:isar-image-base
> + sudo rm -rf tmp
> + sed -i -e 's/#ISAR_USE_CACHED_BASE_REPO ?= "1"/ISAR_USE_CACHED_BASE_REPO ?= "1"/g' conf/local.conf
> bitbake $BB_ARGS \
> multiconfig:qemuarm-stretch:isar-image-base \
> multiconfig:qemuarm64-stretch:isar-image-base \
>
That's a important step.
BTW, what is still missing to do something like this:
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index d8fbfd5..bfefe20 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -144,7 +144,7 @@ do_cache_base_repo() {
fi
}
-addtask cache_base_repo after do_rootfs do_install_imager_deps
+addtask cache_base_repo after do_rootfs do_install_imager_deps before do_build
# Imager are expected to run natively, thus will use the target buildchroot.
ISAR_CROSS_COMPILE = "0"
That would simplify the usage (I always forget how that special target
is called), including CI.
DISCLAIMER: I didn't test this intensively.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-29 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 7:19 Maxim Yu. Osipov
2018-11-29 7:58 ` Jan Kiszka [this message]
2018-11-29 11:33 ` Henning Schild
2018-11-29 12:02 ` Maxim Yu. Osipov
2018-11-29 12:33 ` Henning Schild
2018-11-29 12:40 ` Jan Kiszka
2018-11-29 13:01 ` Maxim Yu. Osipov
2018-11-29 13:26 ` Maxim Yu. Osipov
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=9759704e-9c29-36ba-cbdb-1a252692d34a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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