From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] gtk+/cairo: enable x11 or directfb
Date: Tue, 22 Sep 2015 10:40:57 +0800 [thread overview]
Message-ID: <5600BFB9.1060401@windriver.com> (raw)
In-Reply-To: <CAJTo0LYZ+mcOxm0Tu3E7-sqG08pmtzpkqr3+-r6vESkqOx4S8A@mail.gmail.com>
On 09/19/2015 04:23 AM, Burton, Ross wrote:
>
> On 16 September 2015 at 11:34, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
> Make the world build OK when possible, for example, when no x11 in
> DISTRO_FEATURE.
>
>
> But now you're just explicitly ignoring the directfb DISTRO_FEATURE. Maybe if
> you want to do a world build without X11 enabled the you should add directfb to
> DISTRO_FEATURES?
If I understand correctly, how about we add a sanity check when do world
build? Either X11 or directfb should be in DISTRO_FEATURES. But gtk+ is
the only one which requires this, others can be built without both of them.
// Robert
>
> Ross
next prev parent reply other threads:[~2015-09-22 2:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 2:28 [PATCH 0/4] meta: resend patches Robert Yang
2015-09-16 2:28 ` [PATCH 1/4] gtk+/cairo: enable x11 or directfb Robert Yang
2015-09-16 10:25 ` Jussi Kukkonen
2015-09-16 10:34 ` Robert Yang
2015-09-18 20:23 ` Burton, Ross
2015-09-22 2:40 ` Robert Yang [this message]
2015-09-22 14:12 ` Burton, Ross
2015-09-16 2:28 ` [PATCH 2/4] libsdl: depends on libglu when both x11 and opengl Robert Yang
2015-09-16 2:28 ` [PATCH 3/4] insane.bbclass: fix package_qa_check_buildpaths Robert Yang
2015-09-16 12:38 ` Richard Purdie
2015-09-16 13:56 ` Robert Yang
2015-09-16 15:26 ` Richard Purdie
2015-09-16 2:28 ` [PATCH 4/4] insane.bbclass: make package_qa_clean_path return a relative path Robert Yang
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=5600BFB9.1060401@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.