From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: How to require image recipe from another layer?
Date: Thu, 29 Dec 2011 18:23:59 +0000 [thread overview]
Message-ID: <15061845.WB4g7C0iYD@helios> (raw)
In-Reply-To: <CADzUK1+qXxsQ445f2nJkvCfEM9+nmFTkop74EMK8EDag5brNpQ@mail.gmail.com>
On Thursday 29 December 2011 13:14:20 autif khan wrote:
> The following recipe does not actually put helloworld in the image -
> it does not even build it.
>
> require recipes-sato/images/core-image-sato.bb
> IMAGE_FEATURES += "helloworld"
>
> The following one does.
>
> require recipes-sato/images/core-image-sato.bb
> IMAGE_INSTALL += "helloworld"
>
> I am guessing that if I have several recipes in my layer (say) hw1,
> hw2, hw3 etc, I would have to use the following recipe.
>
> require recipes-sato/images/core-image-sato.bb
> IMAGE_INSTALL += "hw1 hw2 hw3 etc"
>
> However, I am sure there is a way to ties these up with
> "IMAGE_FEATURE" variable.
IMAGE_FEATURES do not refer to individual packages, they are specially defined
package groups (or behaviours in the case of e.g. package-management). If you
have a look at classes/core-image.bbclass and classes/image.bbclass you can
see how the package groups are set up (PACKAGE_GROUP_featurename). As you
found, at the moment there is nothing checking that features in IMAGE_FEATURES
are valid, thus as there is no PACKAGE_GROUP_helloworld and nothing checking
for "helloworld" in IMAGE_FEATURES, it does nothing.
However, if all you want to do is add a few specific packages it's just fine to
add their names to the end of IMAGE_INSTALL - IMAGE_FEATURES might be
overkill.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-29 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 20:06 How to require image recipe from another layer? autif khan
2011-12-28 20:12 ` Chris Larson
2011-12-28 20:22 ` autif khan
2011-12-28 20:31 ` Chris Larson
2011-12-28 20:43 ` autif khan
2011-12-29 18:14 ` autif khan
2011-12-29 18:23 ` Paul Eggleton [this message]
2011-12-29 18:27 ` Chris Larson
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=15061845.WB4g7C0iYD@helios \
--to=paul.eggleton@linux.intel.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.