From: Alexander Kanavin <alex.kanavin@gmail.com>
To: yocto@lists.yoctoproject.org, bratiranjan12@gmail.com
Subject: Re: [yocto] Inter-Task Dependencies
Date: Tue, 5 Mar 2024 12:40:48 +0100 [thread overview]
Message-ID: <CANNYZj9zz1aZMB1JbS-A=N9iw=NBLQa=KMgUWLOdcwkZ-U=K-A@mail.gmail.com> (raw)
In-Reply-To: <a2aO.1709635901197785774.D4bK@lists.yoctoproject.org>
Hello,
It helps if you explain the use case. What is the original file name,
and what is the name of the symlink, and why do you need to create
one?
Alex
On Tue, 5 Mar 2024 at 11:54, Bratiranjan Acharya
<bratiranjan12@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 (#62684): https://lists.yoctoproject.org/g/yocto/message/62684
> Mute This Topic: https://lists.yoctoproject.org/mt/104742073/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2024-03-05 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 10:51 Inter-Task Dependencies Bratiranjan Acharya
2024-03-05 11:40 ` Alexander Kanavin [this message]
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='CANNYZj9zz1aZMB1JbS-A=N9iw=NBLQa=KMgUWLOdcwkZ-U=K-A@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=bratiranjan12@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).