From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 RESEND 1/2] fix: copy boot files after finishing all rootfs operations
Date: Tue, 17 Sep 2024 11:15:06 +0200 [thread overview]
Message-ID: <20240917091507.1714450-1-felix.moessbauer@siemens.com> (raw)
By that, we make sure that all operations (including initrd generation)
are finished before transitioning into the imaging step. Also, this
structures the build into the rootfs and the imaging steps.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
meta/classes/image.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index c29d9e26..0dea06fa 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -363,7 +363,7 @@ do_copy_boot_files() {
cp -f "$dtb" "${DEPLOYDIR}/"
done
}
-addtask copy_boot_files before do_rootfs_postprocess after do_rootfs_install
+addtask copy_boot_files before do_image_tools after do_rootfs
python do_copy_boot_files_setscene () {
sstate_setscene(d)
--
2.39.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20240917091507.1714450-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2024-09-17 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 9:15 'Felix Moessbauer' via isar-users [this message]
2024-09-17 9:15 ` [PATCH v2 RESEND 2/2] delay creation of initrd until end of rootfs install 'Felix Moessbauer' via isar-users
2024-09-17 12:26 ` 'Jan Kiszka' via isar-users
2024-09-18 13:15 ` 'MOESSBAUER, Felix' via isar-users
2025-03-25 13:03 ` 'MOESSBAUER, Felix' via isar-users
2024-09-19 6:56 ` Uladzimir Bely
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=20240917091507.1714450-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox