From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/2 v2] add image-rauc-casync
Date: Fri, 1 Nov 2019 10:17:44 +0100 [thread overview]
Message-ID: <20191101091744.GA22947@lenoch> (raw)
Hi there,
this is second attempt to find out how (if at all) are people using
rauc with casync support. Here it is used to build zip file with
casync update to be deployed on IIS server:
--- 8< ---
#
# We provide this package
#
IMAGE_PACKAGES-$(PTXCONF_IMAGE_RAUC_CASYNC) += image-rauc-casync
#
# Paths and names
#
IMAGE_RAUC_CASYNC := image-rauc-casync
IMAGE_RAUC_CASYNC_VER := $(call ptx/sh, git describe --abbrev=0 --tags)
IMAGE_RAUC_CASYNC_VER_FULL := $(call ptx/sh, git describe --long --tags)
IMAGE_RAUC_CASYNC_DIR := $(BUILDDIR)/$(IMAGE_RAUC_CASYNC)
IMAGE_RAUC_CASYNC_IMAGE := $(IMAGEDIR)/$(IMAGE_RAUC_CASYNC_VER).zip
# ----------------------------------------------------------------------------
# Image
# ----------------------------------------------------------------------------
ifdef PTXCONF_IMAGE_RAUC_CASYNC
IMAGE_RAUC_KEY := $(call ptx/in-platformconfigdir, config/rauc/rauc.key.pem)
IMAGE_RAUC_CERT := $(call ptx/in-platformconfigdir, config/rauc/rauc.cert.pem)
IMAGE_RAUC_KEYRING := $(call ptx/in-platformconfigdir, projectroot/etc/rauc/ca.cert.pem)
TVM4_MANIFEST_FILE := TVM4_$(IMAGE_RAUC_CASYNC_VER).manifest
TVM4_MANIFEST_TEMPLATE := $(call ptx/in-platformconfigdir, config/images/manifest-template)
$(IMAGE_RAUC_CASYNC_IMAGE): $(TVM4_MANIFEST_TEMPLATE)
@$(call targetinfo)
@sed -e 's,@VERSION@,$(IMAGE_RAUC_CASYNC_VER),g' \
-e 's,@VERSIONFULL@,$(IMAGE_RAUC_CASYNC_VER_FULL),g' \
$(TVM4_MANIFEST_TEMPLATE) > $(PTXDIST_TEMPDIR)/$(TVM4_MANIFEST_FILE)
@rauc convert --cert=$(IMAGE_RAUC_CERT) \
--key=$(IMAGE_RAUC_KEY) --keyring=$(IMAGE_RAUC_KEYRING) \
$(IMAGE_RAUC_IMAGE) $(PTXDIST_TEMPDIR)/casync-bundle.raucb
@cd $(PTXDIST_TEMPDIR) && \
zip -q -m -r update.zip casync-bundle.raucb casync-bundle.castr
@zip -q -m -j $(IMAGE_RAUC_CASYNC_IMAGE) $(PTXDIST_TEMPDIR)/update.zip \
$(PTXDIST_TEMPDIR)/$(TVM4_MANIFEST_FILE)
@$(call finish)
endif
--- 8< ---
Ladislav Michl (2):
host-xz: build shared libs again
casync: new package
rules/casync.in | 36 ++++++++++++++++++++
rules/casync.make | 76 ++++++++++++++++++++++++++++++++++++++++++
rules/host-casync.in | 11 ++++++
rules/host-casync.make | 33 ++++++++++++++++++
rules/host-xz.make | 5 ++-
5 files changed, 158 insertions(+), 3 deletions(-)
create mode 100644 rules/casync.in
create mode 100644 rules/casync.make
create mode 100644 rules/host-casync.in
create mode 100644 rules/host-casync.make
--
2.24.0.rc2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-11-01 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 9:17 Ladislav Michl [this message]
2019-11-01 9:18 ` [ptxdist] [PATCH 1/2 v2] host-xz: build shared libs again Ladislav Michl
2019-11-01 9:19 ` [ptxdist] [PATCH 2/2 v2] casync: new package Ladislav Michl
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=20191101091744.GA22947@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.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