From: "Burton, Ross" <ross.burton@intel.com>
To: Piotr Piwko <piotr.piwko@gmail.com>
Cc: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: Check IMAGE_FEATURES content in recipe
Date: Thu, 10 May 2018 10:22:34 +0100 [thread overview]
Message-ID: <CAJTo0LaOOAhnPbUJ2DfWyaty5GM4JBNrGS-+44jt8p+iO4+kqA@mail.gmail.com> (raw)
In-Reply-To: <CAMTWR-Np4pd8tytDdOoabzEZsqU=2w95Y9ddh6UOsD4-F4eDCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On 10 May 2018 at 09:59, Piotr Piwko <piotr.piwko@gmail.com> wrote:
>
>> VAR set in recipe A cannot be accessed by recipe B.
>>
>
> All right, but what about DISTRO_FEATURES? It is available everywhere, so
> maybe there is some possibility to do so ...
>
You need to think about what actually happens. This is a valid bitbake
call:
$ 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.
There are global variables (such as DISTRO_FEATURES) and the *default*
IMAGE_FEATURES is also available globally, but that won't help you here.
Ross
[-- Attachment #2: Type: text/html, Size: 1656 bytes --]
next prev parent reply other threads:[~2018-05-10 9:22 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 [this message]
2018-05-10 15:06 ` Marcelo E. Magallon
2018-05-11 0:04 ` Paul Eggleton
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=CAJTo0LaOOAhnPbUJ2DfWyaty5GM4JBNrGS-+44jt8p+iO4+kqA@mail.gmail.com \
--to=ross.burton@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.