From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: X11 as DISTRO_FEATURE
Date: Thu, 11 Aug 2011 13:17:01 +0100 [thread overview]
Message-ID: <1313065027.6733.127.camel@phil-desktop> (raw)
Right now, there are a bunch of recipes (e.g. dbus, cairo) which always
build against X11 even though the underlying software can work without
it. This makes it somewhat painful to build a display system using
clutter (for example) without X.
It's also moderately fiddly to stop X11 from leaking in by mistake; you
can't just BBMASK the whole of "xorg-*" because things like pixman are
still needed by cairo even when not using X11.
So, to combat this, I would like to make X11 be a DISTRO_FEATURE and
arrange for:
a) libx11 to skip itself; and
b) recipes for which x11 is optional to not depend on X stuff
if that feature isn't selected.
Any objections, better suggestions, ...?
p.
next reply other threads:[~2011-08-11 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 12:17 Phil Blundell [this message]
2011-08-11 13:27 ` X11 as DISTRO_FEATURE Anders Darander
2011-08-11 14:16 ` Phil Blundell
2011-08-11 14:19 ` Andreas Oberritter
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=1313065027.6733.127.camel@phil-desktop \
--to=philb@gnu.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