Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: leo@missingno.tech
To: openembedded-devel@lists.openembedded.org
Cc: leo@missingno.tech
Subject: [meta-oe][PATCH] image_types_sparse: use .sparse extension to create subimage link
Date: Thu,  3 Sep 2026 09:43:03 +0200	[thread overview]
Message-ID: <20260903074303.306722-1-leo@missingno.tech> (raw)

If the image extension (.simg) does not match the CONVERSIONTYPE
(sparse), the function create_symlinks() in oe-core image.bbclass
fails to create the image link for this subimage.
Using the .sparse extension for images produced by the
ext2simg_android tool fixes this and generates a usable image link.

Signed-off-by: Leo Sartre <leo@missingno.tech>
---
 meta-oe/classes/image_types_sparse.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-oe/classes/image_types_sparse.bbclass b/meta-oe/classes/image_types_sparse.bbclass
index 5c1d92bd18..b2a58b8757 100644
--- a/meta-oe/classes/image_types_sparse.bbclass
+++ b/meta-oe/classes/image_types_sparse.bbclass
@@ -16,7 +16,7 @@ CONVERSION_CMD:sparse = " \
     case '${type}' in \
         ext*) \
             bbnote 'Running e2fsprogs-derived ext2simg_android..' ; \
-            ext2simg_android '${IMAGE_NAME}.${type}' '${IMAGE_NAME}.${type}.simg' || bberror 'ext2simg_android failed' \
+            ext2simg_android '${IMAGE_NAME}.${type}' '${IMAGE_NAME}.${type}.sparse' || bberror 'ext2simg_android failed' \
             ;; \
         *) \
             bbnote 'Generating sparse image for non-ext filesystem...'; \
-- 
2.34.1



                 reply	other threads:[~2026-09-03  8:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260903074303.306722-1-leo@missingno.tech \
    --to=leo@missingno.tech \
    --cc=openembedded-devel@lists.openembedded.org \
    /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