<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 20, 2014 at 8:47 AM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":ax" class="a3s" style="overflow:hidden"> (note: more annoying pedantry regarding bitbake configuration and<br>
documentation but, if i'm going to explain this to my students, i<br>
really need to understand it completely.)<br>
<br>
some questions and observations about how bitbake defines some<br>
fetch-related variables as opposed to how those variables are defined<br>
in higher layers such as oe-core and poky. as richard purdie(?)<br>
pointed out recently, the goal should be to document bitbake as<br>
independently as possible from what happens in layers such as oe and<br>
poky, but it seems this is not as clean as it could be.<br>
<br>
consider first bitbake's current bitbake.conf file. first, can we<br>
agree that this set of variables:</div></blockquote></div><br></div><div class="gmail_extra">Before I dive into the remainder of the email, we should note that the bitbake.conf in bitbake is never used when you use oe, it's solely as an example / starting point for other non-oe projects wanting to use bitbake. Presumably it gets forgotten about when changes to bitbake itself are made, and so it's fallen behind.<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>