Can you publish the layer somewhere? It's hard to tell what is going
on, but perhaps you could check which task creates which artefacts in
deploy directory, and consult the bitbake manual about task
dependencies so they can be run in correct order.
Alex
On Thu, 7 Mar 2024 at 11:13, Bratiranjan Acharya
<bratiranja...@gmail.com> wrote:
>
> Okay, In details
> There are base-initramfs.bb, image-ext4.inc, image-ext4-debug.bb files and
> dm-verity file which depends upon the base-initramfs as we know that
> base-initramfs loads the actual rootfs so in image-ext4.inc i wrote a
> custom-task "do_simlink_ext4" inside which i just wrote
> ----------------<
> image-ext4.inc>----------------------------------------------------
> do_image_complete[postfuncs] += "do_simlink_ext4"
> do_simlink_ext4(){
> pushd ${DEPLOY_DIR_IMAGE}
> ln -snf ${IMAGE_EXT4_NAME} azma-image-${MACHINE}.ext4
> popd
> }
> ------------------------------------------------------------------------------------------------
> so as per this after do_image_complete task of image-ext4-debug.bb this
> symlink function must work but after do_image_complete task of
> image-ext4-debug.bb the rootfs which is ${IMAGE_EXT4_NAME} (it is also a
> softlink which points to the actual rootfs with the timestamp) is in the
> deploy dir but this command " ln -snf ${IMAGE_EXT4_NAME}
> azma-image-${MACHINE}.ext4" is creating the softlink whether the rootfs is
> present or not so i have fiven if-else condition too that if the rootfs is
> there then only create the softlink but then this simlink funtion didnot
> worked and one more thing in this base-initramfs.bb file this dependency is
> there
> ----------------< base-initramfs.bb
> >-----------------------------------------------
> "do_rootfs[depends] += image-ext4-debug:do_image_complete"
> ----------------------------------------------------------------------------------------------
> And i want that as we know that the ${IMAGE_EXT4_NAME} (it is also a
> softlink which points to the actual rootfs with the timestamp) rootfs is
> generating and getting deployed to deploy dir after do_image_complete task of
> the image-ext4-debug.bb file then why the softlink is not behaving properly
> please help.
>
> REGARDS
> Brati
>
> On Mon, 4 Mar 2024 at 22:08, Bratiranjan Acharya <bratiranja...@gmail.com>
> wrote:
>>
>> Hi,
>>
>> I hope this email finds you well. I have a question regarding a specific
>> issue that I'd like to discuss. Allow me to provide some context:
>>
>> In the final image bb files, there's a custom task designed to generate a
>> softlink for the rootfs.ext4. Unfortunately, I've had to resort to using the
>> "ln -snf" command, as I'm unsure after which recipe's task the rootfs is
>> generated and deployed to the deploy directory. Therefore, I'm forcefully
>> creating the softlink. Despite attempting various debugging methods, I
>> haven't been able to find a solution yet.As the source is vast and complex.
>>
>> For example, if the rootfs is generated and deployed by a task from another
>> recipe where my custom task isn't present, even using inter-task
>> dependencies flags hasn't yielded results. Could you please provide
>> assistance with this matter? If i can know which recipes task is creating
>> and deploying OR which recipe is deploying the rootfs to ${DEPLOY_DIR} i can
>> solve that.
>>
>> Thank you for your help.
>>
>> Best regards, Brati
>> Yocto Developer
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62723): https://lists.yoctoproject.org/g/yocto/message/62723
Mute This Topic: https://lists.yoctoproject.org/mt/104725909/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
