From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 1/3] meta/classes/image: Call transform_template after rootfs_install
Date: Sun, 12 May 2019 21:30:58 +0200 [thread overview]
Message-ID: <20190512193100.23709-2-mosipov@ilbers.de> (raw)
In-Reply-To: <20190512193100.23709-1-mosipov@ilbers.de>
mkimage fails in do_fit_image (in meta/classes/fit-img.bbclass)
as input fitimage.its file is generated too early by
transform_template when KERNEL_IMG isn't yet properly set.
Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
---
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 f9a3052..fb35a4c 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -169,7 +169,7 @@ do_copy_boot_files() {
cp -f "$dtb" "${DEPLOY_DIR_IMAGE}/${DTB_FILE}"
fi
}
-addtask copy_boot_files before do_rootfs_postprocess after do_rootfs_install
+addtask copy_boot_files before do_rootfs_postprocess do_transform_template after do_rootfs_install
python do_image_tools() {
"""Virtual task"""
--
2.11.0
next prev parent reply other threads:[~2019-05-12 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 19:30 [PATCH v2 0/3] vmlinuz/initrd for the same MACHINE are overwritten Maxim Yu. Osipov
2019-05-12 19:30 ` Maxim Yu. Osipov [this message]
2019-05-12 19:30 ` [PATCH v2 2/3] Revert "image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed" Maxim Yu. Osipov
2019-05-13 7:31 ` Claudius Heine
2019-05-13 7:39 ` Maxim Yu. Osipov
2019-05-13 7:43 ` Maxim Yu. Osipov
2019-05-13 8:11 ` Claudius Heine
2019-05-13 9:01 ` Maxim Yu. Osipov
2019-05-13 11:05 ` Claudius Heine
2019-05-13 11:16 ` Maxim Yu. Osipov
2019-05-14 14:41 ` Maxim Yu. Osipov
2019-05-12 19:31 ` [PATCH v2 3/3] ci: Include qemuarm-buster into fast build/vm_smoke_test Maxim Yu. Osipov
2019-05-14 17:24 ` [PATCH v2 0/3] vmlinuz/initrd for the same MACHINE are overwritten 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=20190512193100.23709-2-mosipov@ilbers.de \
--to=mosipov@ilbers.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