From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: EXCLUDE_FROM_WORLD
Date: Thu, 26 Jul 2012 20:07:19 +0100 [thread overview]
Message-ID: <1343329639.7600.13.camel@ted> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF841FF7D6FA@ALA-MBB.corp.ad.wrs.com>
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.
Chris replied about the other bits...
Cheers,
Richard
next prev parent reply other threads:[~2012-07-26 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 18:45 EXCLUDE_FROM_WORLD Slater, Joseph
2012-07-26 18:56 ` EXCLUDE_FROM_WORLD Chris Larson
2012-07-26 19:07 ` Richard Purdie [this message]
2012-07-26 20:16 ` EXCLUDE_FROM_WORLD Slater, Joseph
2012-07-26 20:35 ` EXCLUDE_FROM_WORLD Richard Purdie
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=1343329639.7600.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox