From: "John Klug" <john.klug@multitech.com>
To: Josef Holzmayr <jester@theyoctojester.info>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] How does one add do_fetch, do_unpack to an image recipe?
Date: Mon, 9 Aug 2021 23:57:40 +0000 [thread overview]
Message-ID: <40ac28433e4749ab957a1c52d3bbf1fd@multitech.com> (raw)
In-Reply-To: <2fc610b2-2a45-f41b-cc63-40af68632c66@theyoctojester.info>
Thanks for your great help. A native recipe is what I needed with data in it only. So my native recipe copies files into ${D}${datadir}/${PN}.
Then my image build uses DEPENDS= to bring in the native recipe.
Then my IMAGE_POSTPROCESS_COMMAND can reference ${STAGING_DATADIR_NATIVE}/[native recipe name] to find the data it needs.
Then I don't need to patch the bbclass file.
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> on behalf of Josef Holzmayr <jester@theyoctojester.info>
Sent: Monday, August 9, 2021 12:41 AM
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] How does one add do_fetch, do_unpack to an image recipe?
Howdy!
Am 07.08.2021 um 02:25 schrieb John Klug:
> I am using dunfell.
>
> In the documentation I see:
>
> http://mail2.multitech.com:32224/?dmVyPTEuMDAxJiYyOTU2NDk0NDY2NmQ1NDQyND02MTEwQzAxOF8yMDIxXzcwNzFfMSYmYjc2MzZjMTgxNGE4NTkzPTIzMzMmJnVybD1odHRwcyUzQSUyRiUyRnd3dyUyRXlvY3RvcHJvamVjdCUyRW9yZyUyRmRvY3MlMkZjdXJyZW50JTJGYml0YmFrZS11c2VyLW1hbnVhbCUyRmJpdGJha2UtdXNlci1tYW51YWwlMkVodG1sJTIzdW5zZXR0aW5nLXZhcmlhYmxlcw==
>
> In case some filter removes the yocto URL, I am referring to:
>
> docs/current/bitbake-user-manual/bitbake-user-manual.html#unsetting-variables
>
> Which has this example:
>
> unset do_fetch[noexec]
>
> If I put this in my image recipe, the do_fetch noexec item still exists.
>
> In order to fix this problem I had to patch openembedded-core/meta/classes/image.bbclass, and remove the line setting do_fetch[noexec]="1" and the ones following.
>
> I need to do a fetch for my IMAGE_POSTPROCESS_COMMAND.
From first glance, I'd guess that the approach is just not correct. If
that thing to be fetched also needs to go *into* the image: make it a
recipe on its own. If you only need it during build time, then it should
probably be a -native dependency, and therefore again a recipe on its
own. Then the image recipe can depend on it and use its contents during
the build/postprocess stage.
Greetz
>
>
> Thanks.
>
>
>
>
>
prev parent reply other threads:[~2021-08-09 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 0:25 How does one add do_fetch, do_unpack to an image recipe? John Klug
2021-08-09 5:41 ` [yocto] " Josef Holzmayr
2021-08-09 23:57 ` John Klug [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=40ac28433e4749ab957a1c52d3bbf1fd@multitech.com \
--to=john.klug@multitech.com \
--cc=jester@theyoctojester.info \
--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