[bitbake-devel] some preliminary questions about bitbake manual

[Paul Eggleton]

On Monday 19 March 2012 07:49:59 Robert P. J. Day wrote:
>   i'm about to write some tutorials on OE/bitbake/poky/yocto (from a
> position of moderate ignorance, hoping that will change), so a couple
> questions/observations before i get started.
> 
>   at risk of repetition, i already noted that if you google on
> "bitbake user manual", you end up here:
> 
>   http://bitbake.berlios.de/manual/
> 
> which is *way* out of date, so perhaps a link to something newer would
> be useful.

Yes, we acknowledge it is quite out of date. The problem with the BitBake 
manual is it must cover only BitBake generically, and not OE. Of course 
there's a lot that could be added to it, but having complete documentation 
there is less important than documenting OE. That's not to say we won't 
welcome patches though ;)

>   next, is it fair to say that the current version of the bitbake
> manual is the one that's part of bitbake itself, in the doc/
> directory?  so if i want to submit some patches, i'd post them to this
> list and those patches would always be relative to my current "git
> pull" of bitbake?

Yes, that's correct.
 
>   finally (for now), over at yocto, here's a quick tutorial on getting
> started with oe-core:
> 
>   https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core
> 
> it all looks reasonable but what you end up with in the oe-core
> directory is two "bitbake.conf" files:
> 
> $ find . -name bitbake.conf
> ./meta/conf/bitbake.conf
> ./bitbake/conf/bitbake.conf
> $
> 
>   i'm assuming that's by design and there are no weird conflicts
> between the two files, right?

Sort of - the last one is actually an example config and since it never ends up 
in BBPATH it will never be used. Now that you mention it, Richard mentioned to 
me recently that it should probably be renamed to bitbake.conf.sample to avoid 
confusion.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre