From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Piotr Piwko <piotr.piwko@gmail.com>
Subject: Re: Check IMAGE_FEATURES content in recipe
Date: Fri, 11 May 2018 12:04:13 +1200 [thread overview]
Message-ID: <3277264.MICTcM6872@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <20180510150603.m2u5s53z6c7zc3uh@nyx.americas.hpqcorp.net>
On Friday, 11 May 2018 3:06:11 AM NZST Marcelo E. Magallon wrote:
> On Thu, May 10, 2018 at 10:22:34AM +0100, Burton, Ross wrote:
>
> >$ bitbake image-foo image-bar
> >
> >image-foo and image-bar both contain recipe-flob. recipe-flob will be
> >built *once* to generate the packages, and those packages used to build
> >both images. If image-foo is read-only and image-bar is read/write, the
> >*same packages* will be reused. recipe-flob has no idea that foo is
> >read-only and bar is read/write because the IMAGE_FEATURES assignments are
> >specific to those image recipes.
>
> When dealing with a somewhat similar problem, what I've done is
> that my-recipe.bb generates two packages (my-package-a,
> my-package-b) and the images select which of the two packages
> they want to use.
Right, that's another solution.
FYI I have covered these in the technical FAQ:
https://wiki.yoctoproject.org/wiki/Technical_FAQ#How_do_I_change_how_my_recipe_is_built_depending_on_what_image_I.27m_building.3F
(One day we'll figure out how to place this somewhere where people can more
easily find it).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2018-05-11 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 7:37 Check IMAGE_FEATURES content in recipe Piotr Piwko
2018-05-10 8:46 ` ChenQi
2018-05-10 8:54 ` André Draszik
2018-05-10 8:59 ` Piotr Piwko
2018-05-10 9:22 ` Burton, Ross
2018-05-10 15:06 ` Marcelo E. Magallon
2018-05-11 0:04 ` Paul Eggleton [this message]
2018-05-10 10:54 ` Alexander Kanavin
2018-05-10 11:29 ` Piotr Piwko
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=3277264.MICTcM6872@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=piotr.piwko@gmail.com \
--cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.