[oe] bitbake and OE opperation

[Lee Studley]

Wow the price has jumped, but use the Student license: $49 version


At 11:37 AM 3/22/2007 -0700, you wrote:
>Hi,
>I personally like www.activestate.com/Products/Komodo/   komodo
>( linux and Windows ) for searching large projects. About $30 and is well
>worth it.
>
>It has good grepping and module/object search tools. It can do single
>stepping and breakpoints in Python ( and other langs ) within the gui and
>some pretty good variable watch windows.
>-Lee
>
>
>At 02:34 PM 3/22/2007 +0000, you wrote:
> >Hi,
> >
> >On Mon, 2007-03-19 at 20:31 -0700, Mark Gross wrote:
> > > I'm trying to understand the way bit bake builds the dependency trees
> > > and works at a low level.   Trying to reverse engineer it from the
> > > python code is difficult.  Does anyone recommend any browser tools for
> > > navigating a large python code base like bit bake?
> >
> >I don't have any tools to recommend to help with this but you might find
> >the recent trunk versions easier to follow as the parts are more split
> >into modules.
> >
> > > I've read the documentation pages I could find but I haven't found any
> > > "theory of operation" types of documents.  Are there any such things?
> >
> >Did you read the bitbake manual? If so, thats around as low level as the
> >documentation goes since most OE users don't usually need to delve into
> >what bitbake does behind the scenes and the manual is a mostly complete
> >document of its API.
> >
> >If you are interested, there are emails in the archive talking about
> >specific changes that have been made to the code such as multithreading.
> >Also, if there is anything you want clarified, I'm happy to explain
> >things if I can.
> >
> > > The questions I have are:
> > > How does a simple command line "bitbake slogos-image" translate into
> > > building all the components?
> >
> >Bitbake only looks at a small subset of the metadata and is conceptually
> >quite simple. Speaking in simply terms, bitbake looks at what each file
> >PROVIDES and also what each file DEPENDS on.
> >
> >Once it has a target, it can look at what dependencies it needs (from
> >DEPENDS and maybe RDEPENDS). It can then find providers for those
> >dependencies which can be influenced by things like PREFERRED_PROVIDER
> >and PREFERRED_VERSION. This cycle then repeats until it has a build
> >chain. It converts that chain into a list of tasks and then executes
> >each task in turn.
> >
> >In bitbake trunk, taskdata.py generates the metadata model in memory and
> >then runqueue.py "compiles" that metedata into a single queue and builds
> >it. If a task fails, it can recompile the metadata and try a different
> >build path should the user wish.
> >
> >Note that bitbake 1.6 or less handles this totally differently and the
> >code was rewritten in 1.7 onwards.
> >
> > > How does bitbake push in the ./configure command line options?
> >
> >Bitbake knows nothing about this, it just knows about a list of tasks.
> >autotools.bbclass defines a do_configure task which knows how to pass
> >options set in an EXTRA_OECONF variable to a configure commandline. The
> >classes are a powerful abstraction feature but are part of OE, not
> >bitbake.
> >
> > > Are there tools for doing analysis on the open embedded bb library?
> >
> >What kind of analysis?
> >
> >Regards,
> >
> >Richard
> >
> >
> >
> >
> >_______________________________________________
> >Openembedded-devel mailing list
> >Openembedded-devel at lists.openembedded.org
> >http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>_______________________________________________
>Openembedded-devel mailing list
>Openembedded-devel at lists.openembedded.org
>http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel