public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, yi liu <liuyi@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: Duplicated dtb files issue for multiple confiugrations
Date: Wed, 5 Jun 2024 18:23:14 +0200	[thread overview]
Message-ID: <776ce590-0c44-4c1a-b01e-4bd09d4f0927@siemens.com> (raw)
In-Reply-To: <ea563579c20c8bbf2d8c316d27ad7e31af1dbe60.camel@ilbers.de>

On 04.06.24 14:38, Uladzimir Bely wrote:
> On Mon, 2024-06-03 at 05:46 -0700, 'yi liu' via isar-users wrote:
>> Hi all,
>>
>> I am trying to make use of isar image installer to create the
>> installer for some distro based on meta-iot2050
>> (https://github.com/siemens/meta-iot2050). During the build process,
>> I got error below:
>>
>> |ERROR: mc:isar-installer:isar-image-installer-1.0-r0
>> do_copy_boot_files: The recipe isar-|image-installer is trying to
>> install files into a shared area when those files already exist.
>> |Those files and their manifest location are:
>> |  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-m2.dtb
>> |    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
>> |  /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic.dtb
>> |    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
>> |  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-
>> pg2.dtb
>> |    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
>> |  /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic-pg2.dtb
>> |    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
>> |  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced.dtb
>> |    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
>> |  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-sm.dtb
>> |    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
>> |Please verify which recipe should provide the above files.
>>
>> It looks like the isar image installer utilizes multiple
>> configurations to build the installer image and the target image at
>> the same time. After searching from the mail list, I found this issue
>> has been reported in other threads with similar cases (building
>> multiple images for the same machine):
>> - https://groups.google.com/g/isar-users/c/qAnjahjjfsw
>> - https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
>> - https://groups.google.com/g/isar-users/c/ZMD4XY4dKWQ
>> - https://groups.google.com/g/isar-users/c/PSGU_AcdPZ8
>>
>> Is anyone still working on this issue? 
>>
>> Best Regards,
>> Liu Yi
>> -- 
>> 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/c426ad86-5cc5-42e6-8223-e7a7e5b3424en%40googlegroups.com
>> .
> 
> Hello.
> 
> Have you tried the patch from
> "https://groups.google.com/g/isar-users/c/qAnjahjjfsw discussion? Does
> it work for you case with installer?
>  
> It's still not merged to Isar since it may break some downstreams that
> could expect DTB files in their current location in deploy directory.
> 

The patch wasn't merge as we agreed that it is not the best way forward.
We should rather look into avoiding deploy dir for the DTB distribution
(and only come back to it if that turns out to be impossible).

Jan

-- 
Siemens AG, Technology
Linux Expert Center


  reply	other threads:[~2024-06-05 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 12:46 yi liu
2024-06-04 12:38 ` Uladzimir Bely
2024-06-05 16:23   ` Jan Kiszka [this message]
2024-06-06  7:24   ` Yi Liu
2024-06-10 10:10     ` Baurzhan Ismagulov

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=776ce590-0c44-4c1a-b01e-4bd09d4f0927@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=liuyi@siemens.com \
    --cc=ubely@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