<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 25, 2013 at 12:38 PM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":17r">* similar to world target, but collects all PACKAGES<br>
* recipes marked with EXCLUDE_FROM_WORLD are excluded from world as well<br>
as world-image<br>
* recipes marked with EXCLUDE_FROM_WORLD_IMAGE are excluded completely<br>
from world-image, sometimes you can build 2 recipes in same sysroot,<br>
but cannot install them in the same image<br>
* PACKAGES listed in EXCLUDE_PACKAGES_FROM_WORLD_IMAGE are also<br>
excluded. You can remove e.g. ${PN}-dbg, but keep all other PACKAGES.<br>
<br>
Signed-off-by: Martin Jansa <<a href="mailto:Martin.Jansa@gmail.com">Martin.Jansa@gmail.com</a>></div></blockquote></div><br>bitbake should have zero knowledge of what an image even is, much less hardcoding awareness of the IMAGE_INSTALL variable. Instead, we should provide a means to hook into bitbake's knowledge of the recipes included in the world image, and let a world-image recipe utilize that.<br>
-- <br>Christopher Larson</div></div>