From: Henning Schild <henning.schild@siemens.com>
To: Harald Seiler <hws@denx.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta: Add targz image class
Date: Tue, 20 Nov 2018 13:51:19 +0100 [thread overview]
Message-ID: <20181120135119.119185af@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <525a1c5b7730f98e1236e1596cf31dc3e23e1b5e.camel@denx.de>
Am Tue, 20 Nov 2018 12:50:24 +0100
schrieb Harald Seiler <hws@denx.de>:
> Signed-off-by: Harald Seiler <hws@denx.de>
> ---
> meta/classes/targz-img.bbclass | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
> create mode 100644 meta/classes/targz-img.bbclass
>
> diff --git a/meta/classes/targz-img.bbclass
> b/meta/classes/targz-img.bbclass new file mode 100644
> index 0000000..898c2a8
> --- /dev/null
> +++ b/meta/classes/targz-img.bbclass
> @@ -0,0 +1,12 @@
> +# This software is a part of ISAR.
> +
> +TARGZ_IMAGE_FILE = "${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.tar.gz"
> +
> +do_targz_image[stamp-extra-info] = "${DISTRO}-${MACHINE}"
> +
> +do_targz_image() {
> + rm -f ${TARGZ_IMAGE_FILE}
Can be skipped, probably fails anyways.
> + sudo tar -cvzf ${TARGZ_IMAGE_FILE} -C ${IMAGE_ROOTFS} .
> +}
> +
> +addtask targz_image before do_build after do_copy_boot_files
"after do_rootfs" in fact we do not need the copy for that one
How will we test that?
Henning
next prev parent reply other threads:[~2018-11-20 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 11:50 Harald Seiler
2018-11-20 11:54 ` Jan Kiszka
2018-11-20 12:51 ` Henning Schild [this message]
2018-11-20 13:07 ` Harald Seiler
2018-11-20 13:14 ` chombourger
2018-11-20 13:19 ` [PATCH v2] " Harald Seiler
2018-11-23 7:32 ` Maxim Yu. Osipov
2018-11-23 11:38 ` Harald Seiler
2018-11-24 14:01 ` Cedric Hombourger
2018-11-27 9:13 ` [PATCH v3] " Harald Seiler
2018-12-10 12:04 ` 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=20181120135119.119185af@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=hws@denx.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