On 6/15/21 9:15 AM, Richard Purdie wrote:
> On Tue, 2021-06-15 at 16:50 +0300, Petr Nechaev wrote:
>> Hi All,
>>
>> I've been using bitbake for >5 years now, however I do not understand
>> the nature of the problem at all. Could you clarify what the problem is
>> i.e. what's the difference between these lines:
>>
>> IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
>> VAR_A = "${VAR_B}"
>
> Consider this example where the BSP sets:
>
> IMAGE_FSTYPES = "tar"
> IMAGE_FSTYPES_somemachine = "ext4"
> INITRAMFS_FSTYPES = "cpio"
> OVERRIDES = "${MACHINE}"
>
> then the initramfs image recipe does:
>
> IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
>
>
> Given that config, if you set MACHINE = "somemachine", which image
> type would you expect the initramfs image to have?
>
>
> The answer is that it will try and generate an ext4 initramfs.
> What you'd expect/want is a cpio initramfs.
>
> The reason is that the machine override, i.e.:
>
> IMAGE_FSTYPES_somemachine = "ext4"
>
> cannot be undone.
I've hit this issue in the past (different context, but I believe the same
issue). What I end up doing is (in the initramfs) is effectively:
OVERRIDES .= ":ramfs"
IMAGE_FSTYPES_ramfs = "cpio"
doing this in the recipe (or a bbclass that should only be loaded by a recipe)
ensures that we can set IMAGE_FSTYPE to a specific value, and avoids the
specific issue mentioned here.
(At least it worked well in the case I needed it for, not sure if it would here,
but it may be what is needed.)
--Mark
> Cheers,
>
> Richard
>
>
>
>
>
>
>
>
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1240):
https://lists.openembedded.org/g/openembedded-architecture/message/1240
Mute This Topic: https://lists.openembedded.org/mt/83552628/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
