[oe] some ipk contents missed in rootfs - fuse_2.7.4

mgundes mgcse at hotmail.com
Wed Jan 4 23:17:41 UTC 2012


On Thu, Jan 5, 2012 at 12:40 AM, Khem Raj <raj.khem at gmail.com> wrote:

> On Wed, Jan 4, 2012 at 2:00 PM, mgundes <mgcse at hotmail.com> wrote:
> > At that point, can I say this as a result: "IMAGE_INSTALL is checked by
> > bitbake and just only ipks of in that variable are added to rootfs. In my
> > case, I had added fuse to IMAGE_INSTALL and just fuse*.ipk was added to
> > rootfs, so that I needed to adding fuse-utils to IMAGE_INSTALL to get
> > contents of fuse-utils*.ipk in my rootfs."
> >
> > Is that conclusion true?
> >
>
> you have to understand the difference between recipe name and output
> package name
> one recipe may emit multiple packages. What goes into image is picked
> from output package
> names and not recipe names. By default bitbake translates recipe name
> to be one of packages
> name as well. e.g. if you have foo.bb then there will be a foo.ipk
> generated but there might
> be more like foo-utils.ipk etc. if you did that in the recipe.
>
>
Yes, one bb can generate many ipks as defined by PACKAGES variable.
Just I want to be sure; up to your example, If I need foo.ipk and
foo-utils.ipk contents in my rootfs do I need to add "foo foo-utils" or
just "foo" to IMAGE_INSTALL?


> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>


-- 
MahmutG



More information about the Openembedded-devel mailing list