All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: gokhan.cetin@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [isar-cip-core][PATCH 1/1] add missing dependency to template subst in swu
Date: Wed, 12 Apr 2023 14:41:18 +0800	[thread overview]
Message-ID: <20230412064118.431415-1-felix.moessbauer@siemens.com> (raw)

Before creating swu files, the sw-description temlate needs to be
expanded. This logic is also independent of the imagetype.
Previously, only some image types had this task in the dependency chain
before invoking the swu creation. By that, it was working for e.g. wic,
but not for ext4 rootfs images (referring to the type of the abrootfs).

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 classes/swupdate.bbclass | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/classes/swupdate.bbclass b/classes/swupdate.bbclass
index 064d0ad..e12a4d2 100644
--- a/classes/swupdate.bbclass
+++ b/classes/swupdate.bbclass
@@ -9,6 +9,9 @@
 #  Felix Moessbauer <felix.moessbauer@siemens.com>
 #
 # SPDX-License-Identifier: MIT
+
+inherit template
+
 SWU_ROOTFS_TYPE ?= "squashfs"
 SWU_ROOTFS_NAME ?= "${IMAGE_FULLNAME}"
 # compression type as defined by swupdate (zlib or zstd)
@@ -50,6 +53,7 @@ def get_swu_compression_type(d):
 # We append to the path, so locally provided config files are preferred
 FILESEXTRAPATHS:append = ":${LAYERDIR_cip-core}/recipes-core/images/swu"
 
+do_image_swu[depends] += "${PN}:do_transform_template"
 do_image_swu[stamp-extra-info] = "${DISTRO}-${MACHINE}"
 do_image_swu[cleandirs] += "${WORKDIR}/swu"
 IMAGE_CMD:swu() {
-- 
2.39.2



             reply	other threads:[~2023-04-12 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  6:41 Felix Moessbauer [this message]
2023-04-13 19:16 ` [isar-cip-core][PATCH 1/1] add missing dependency to template subst in swu Jan Kiszka

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=20230412064118.431415-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=gokhan.cetin@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.