From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: understanding what's in an image
Date: Tue, 10 Jan 2012 07:57:48 -0700 [thread overview]
Message-ID: <4F0C51EC.1030401@mlbassoc.com> (raw)
In-Reply-To: <4F0C4FBF.6080100@gmail.com>
On 2012-01-10 07:48, Jim Abernathy wrote:
> On 01/09/2012 09:07 PM, Christopher Larson wrote:
>> Read layer.conf in each layer. See the BBFILES variable.
>> --
>> Christopher Larson
>>
>> On Monday, January 9, 2012 at 5:51 PM, James Abernathy wrote:
>>
>>> I'm trying to understand how bitbake parses the poky directory tree a little better.
>>>
>>> The best I can figure all .bb files are NOT included. Just some of them are. I'm guessing that the .bb in the meta/recipe-sato named core-image-sato.bb is the one that is used
>>> to start the parsing if bitbake core-image-sato is executed.
>>> I originally thought all subdirectories of a path included in BBLAYER were parsed looking for .bb files, but now I know that is not true, but not sure why.
>>>
>>> For example, it does not appear that webkit is included in the core-image-sato even though the recipe-sato directory includes the webkit subdirectory with it's recipe. What
>>> would be the proper way of adding the webkit to core-image-sato??
>>>
>>> Jim A
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
> the layer.conf in meta/conf includes and covers all .bb files under it like receipe-sato, which includes web-webkit. So does this say that the web-webkit get's built by bitbake,
> but the images does not contain web-webkit until you put in the IMAGE_INSTALL += "web-webit"???
No, only packages which are needed to satisfy the needs of
the given image are built. So, if your image does not include
web-webkit, it won't be built even though there is a recipe
for it.
When building an image, bitbake looks at the image recipe and
figures out what packages are needed (these are listed explicitly).
Then any additional packages which are needed (DEPENDS, RDEPENDS, etc)
will be added to the list. This process continues until all
dependencies are met, yielding the final package set. Out of
the 1000 or so possible recipes, you may end up only building
a few hundred and many of these are support - i.e. only used
for the build process itself.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-01-10 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 0:51 understanding what's in an image James Abernathy
2012-01-10 2:07 ` Christopher Larson
2012-01-10 14:48 ` Jim Abernathy
2012-01-10 14:57 ` Gary Thomas [this message]
2012-01-10 15:02 ` Jim Abernathy
2012-01-10 12:03 ` Gary Thomas
2012-01-10 12:23 ` James Abernathy
2012-01-10 12:36 ` Gary Thomas
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=4F0C51EC.1030401@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.