<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 20, 2014 at 8:55 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 class="">On Fri, 20 Jun 2014, Christopher Larson wrote:<br>
<br>
><br>
> On Fri, Jun 20, 2014 at 8:47 AM, Robert P. J. Day <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br>
> (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:<br>
><br>
><br>
> Before I dive into the remainder of the email, we should note that<br>
> the bitbake.conf in bitbake is never used when you use oe, it's<br>
> solely as an example / starting point for other non-oe projects<br>
> wanting to use bitbake. Presumably it gets forgotten about when<br>
> changes to bitbake itself are made, and so it's fallen behind.<br>
<br>
</div> oh, i realize that but (i think) my main point was that it seems<br>
almost impossible to document bitbake completely stand-alone when<br>
almost everyone is going to use it in the context of a higher layer<br>
like OE, and there just seem to be unnecessary inconsistencies between<br>
bitbake and OE that make the bitbake user manual confusing.</blockquote></div><br></div><div class="gmail_extra">Fair enough. An argument could be made that oe-core *is* the example of how to use bitbake, but the problem with that is, the bitbake.conf there doesn't differentiate between what's required for bitbake / what vars are obeyed specifically by bitbake and the vars that are obeyed by oe-core's classes, so a non-oe project would have difficulty in paring it down to what they need for their own projects.<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>