On Thu, 2012-07-26 at 20:16 +0000, Slater, Joseph wrote: > > > -----Original Message----- > > From: openembedded-core-boun...@lists.openembedded.org > > [mailto:openembedded-core- > > boun...@lists.openembedded.org] On Behalf Of Richard Purdie > > Sent: Thursday, July 26, 2012 12:07 PM > > To: Patches and discussions about the oe-core layer > > Subject: Re: [OE-core] EXCLUDE_FROM_WORLD > > > > On Thu, 2012-07-26 at 18:45 +0000, Slater, Joseph wrote: > > > Could somebody clarify excluding things from world? I see > > > EXCLUDE_FROM_WORLD = "1" in > > > > > > many places, including libx11.inc, and I'm sure there's plenty of > > > libx11 stuff in world. > > > > The issue is that there are multiple providers of libx11 and when you > > bitbake world, we don't want them all to build. For that reason it gets > > excluded and then the correct version will get built as needed. > > > > There are plans afoot to merge those different libx11 recipes at which > > point the exclude from world will get dropped. > > > > > I also see package specific exclusions in world-broken.inc. > > > > This was originally a list of known problematic packages and used to be > > quite large. Looking at the list: > > > > gobject-introspection: Totally broken recipe, I'm tempted to delete it. > > eds-tools: Again, I'm tempted to delete the recipe > > clutter-box2d: This should build, not sure why its on the broken list. > > Thanks for the clarifications. I would think that there would be packages > that you'd want to exclude conditionally. Like i-only-build-for-x86.bb would > not be part of world for ppc builds. Maybe such packages just cannot ever > be in world, or maybe we do something where EXCLUDE_FROM_WORLD gets computed > from, say, MACHINE_FEATURES?
For those we have COMPATIBLE_MACHINE and COMPATIBLE_HOST. Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core