<div dir="ltr">On 10 May 2018 at 09:59, Piotr Piwko <span dir="ltr"><<a href="mailto:piotr.piwko@gmail.com" target="_blank">piotr.piwko@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div class="m_2303106346380240168m_-3825394283286796240moz-cite-prefix"><br>VAR set in recipe A cannot be accessed by recipe B.<br></div></div></blockquote><div><br></div></span><div>All right, but what about DISTRO_FEATURES? It is available everywhere, so maybe there is some possibility to do so ...</div></div></div></blockquote><div><br></div><div>You need to think about what actually happens. This is a valid bitbake call:</div><div><br></div><div>$ bitbake image-foo image-bar</div><div><br></div><div>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.</div><div><br></div><div>There are global variables (such as DISTRO_FEATURES) and the *default* IMAGE_FEATURES is also available globally, but that won't help you here.</div><div><br></div><div>Ross</div></div></div></div>