From: Mark Gross <markgross@thegnar.org>
To: openembedded-devel@lists.openembedded.org
Subject: bitbake and OE opperation
Date: Mon, 19 Mar 2007 20:31:20 -0700 [thread overview]
Message-ID: <20070320033120.GA8678@thegnar.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
I'm trying to wrap my head around bit bake and the open embedded recipe
files design and structure.
Also, I'm a relative newbie WRT Python.
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'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?
The questions I have are:
How does a simple command line "bitbake slogos-image" translate into
building all the components?
How does bitbake push in the ./configure command line options?
Are there tools for doing analysis on the open embedded bb library?
Thanks,
--mgross
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2007-03-20 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 3:31 Mark Gross [this message]
2007-03-22 14:34 ` bitbake and OE opperation Richard Purdie
2007-03-22 18:37 ` Lee Studley
2007-03-22 18:43 ` Lee Studley
2007-03-23 4:31 ` Mark Gross
2007-03-23 9:20 ` Richard Purdie
2007-03-23 13:09 ` Mark Gross
2007-03-28 17:54 ` Tim Bird
2007-03-28 19:15 ` Richard Purdie
2007-03-28 20:10 ` Tim Bird
2007-03-28 20:19 ` Koen Kooi
2007-03-28 21:12 ` Philip Balister
2007-03-28 21:34 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070320033120.GA8678@thegnar.org \
--to=markgross@thegnar.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.