From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 2/2] Revert "meta/classes/image: Call transform_template after rootfs_install"
Date: Mon, 20 May 2019 09:19:41 +0200 [thread overview]
Message-ID: <729803d9-2ce2-4de4-c121-a7d1d90842a7@siemens.com> (raw)
In-Reply-To: <7de18f5d-e5ca-49ba-2497-ab70a0508c66@ilbers.de>
Hi Maxim,
On 17/05/2019 12.58, Maxim Yu. Osipov wrote:
> On 5/16/19 2:50 PM, claudius.heine.ext@siemens.com wrote:
>> From: Claudius Heine <ch@denx.de>
>>
>> This 'fix' is no longer necessary.
>
> Why did you put fix in quotes?
Because this change just painted over the underlying issue with the
non-deterministic and volatile value of the KERNEL_IMAGE and
INITRD_IMAGE variables. So I would not consider that a permanent fix but
a quick band-aid.
> This revert fixed the problem with do_fit_image if we want to keep old
> naming scheme for kernel/initrd image.
This is not just a naming scheme change. Any bitbake variable that could
change in the middle of the build process is not deterministic an
therefor a bug.
A good next refactoring step would in fact be to remove the
'get_image_name' function, since it does not return a deterministic
value, and instead implement that completely in the `do_copy_boot_files`
task.
Claudius
>
> Maxim.
>
>> This reverts commit 2df0b261610f38bc1d5472f7ee0e3d51243ed602.
>> ---
>> 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 398275f..3eb261f 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
>> do_transform_template after do_rootfs_install
>> +addtask copy_boot_files before do_rootfs_postprocess after
>> do_rootfs_install
>> python do_image_tools() {
>> """Virtual task"""
>>
>
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2019-05-20 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 12:50 [PATCH 0/2] Fix of #56 claudius.heine.ext
2019-05-16 12:50 ` [PATCH 1/2] image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed claudius.heine.ext
2019-05-16 13:32 ` Claudius Heine
2019-05-16 12:50 ` [PATCH 2/2] Revert "meta/classes/image: Call transform_template after rootfs_install" claudius.heine.ext
2019-05-17 10:58 ` Maxim Yu. Osipov
2019-05-20 7:19 ` Claudius Heine [this message]
2019-05-20 19:47 ` Baurzhan Ismagulov
2019-05-21 8:06 ` Claudius Heine
2019-05-18 11:35 ` [PATCH 0/2] Fix of #56 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=729803d9-2ce2-4de4-c121-a7d1d90842a7@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.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