On Friday, January 20, 2012 at 1:33 PM, Khem Raj wrote: > On Fri, Jan 20, 2012 at 9:10 AM, Chris Larson <kerg...@gmail.com > (mailto:kerg...@gmail.com)> wrote: > > On Thu, Jan 19, 2012 at 11:28 PM, Khem Raj <raj.k...@gmail.com > > (mailto:raj.k...@gmail.com)> wrote: > > > I added to local.conf > > > EXTRA_IMAGE_FEATURES += "tools-debug" > > > > > > and now when I do bitbake -g I see that its wanting to build > > > "tools-testapp" and "tools-profile" > > > even though I did not ask them to be added to my image. all these > > > packages are coming from > > > single recipe task-core-tools.bb. If I divide this recipe into 3 > > > different recipes where each provides > > > just one task, it then leaves the others out. > > > > > > Since these are meta packages they pull in a lot of stuff. Would it be > > > ok to divide this recipe > > > into 3 individual recipes ? Ideally I would expect that the other > > > packages dont get build even > > > though they are in same recipe but that is not the case at present > > > > > > > > > > > One option would be to avoid the task indirection and simply set > > PACKAGE_GROUP_tools-debug = "<list of debug tools>" > > > > > we do lot of overriding in those tasks it would get > a bit ugly I guess if we moved that info to image.bbclass > >
Possibly, but note that it doesn't need to live in a class, either. At mentor, our distro has a .inc that defines a variety of package groups for our images. -Chris
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
