From: Gary Thomas <gary@mlbassoc.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: understanding what's in an image
Date: Tue, 10 Jan 2012 05:36:38 -0700 [thread overview]
Message-ID: <4F0C30D6.9010209@mlbassoc.com> (raw)
In-Reply-To: <205064BA-C265-4A33-8449-7118FF11AB9D@gmail.com>
On 2012-01-10 05:23, James Abernathy wrote:
>
> On Jan 10, 2012, at 7:03 AM, Gary Thomas wrote:
>
>> On 2012-01-09 17:51, 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??
>>
>> The 'webkit' is just a library used to build tools such as a
>> web browser. You might want to start with an application that
>> actually uses webkit, such as web-webkit.
>>
>> To build an image which includes web-webkit, add this line to
>> your local.conf file and rebuild the image:
>> IMAGE_INSTALL += "web-webkit"
>>
>> You can also build packages which are not installed into your
>> image by default and use a package manager (e.g. zypper) to
>> install the package later onto a running system.
>>
> This was very helpful. Before I got your email, I had gotten the advice to
> put the IMAGE_INSTALL += "web-webkit" into the core-image-sato.bb file.
> Both seem to work. Not sure which is the best approach. Maybe creating a .bbappend
> in my BSP??
It's seldom a good idea to modify anything in the Yocto core unless that
change should be pushed to everyone. Make the changes you need in your
local layers.
If you're building a specialized system/image for your target, you should
probably consider making your own "image" recipe. The easiest way is to
start with one of the extant image recipes and modifying it for your needs.
>
> So how do I know which applications are installed in an image? is there a how file of IMAGE_INSTALL statements?
You could use hob to see which packages are in your image.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2012-01-10 12:36 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
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 [this message]
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=4F0C30D6.9010209@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=jfabernathy@gmail.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.