Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/8] mesa: enable GLES v1 and v2
Date: Sun, 19 Aug 2012 10:51:17 +0100	[thread overview]
Message-ID: <1345369877.27428.84.camel@ted> (raw)
In-Reply-To: <b34f64c55847fdc3bae12b7954e4ad9f90a6f2b9.1344884283.git.ross.burton@intel.com>

On Mon, 2012-08-13 at 19:58 +0100, Ross Burton wrote:
> Patch originally by Damien Lespiau <damien.lespiau@intel.com>.
> 
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
>  meta/recipes-graphics/mesa/mesa-common.inc |   12 ++++++++++--
>  meta/recipes-graphics/mesa/mesa-dri.inc    |    2 ++
>  2 files changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-graphics/mesa/mesa-common.inc b/meta/recipes-graphics/mesa/mesa-common.inc
> index aac3bbe..24cc3d0 100644
> --- a/meta/recipes-graphics/mesa/mesa-common.inc
> +++ b/meta/recipes-graphics/mesa/mesa-common.inc
> @@ -12,7 +12,7 @@ SECTION = "x11"
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM = "file://docs/license.html;md5=03ccdc4c379c4289aecfb8892c546f67"
>  
> -INC_PR = "r0"
> +INC_PR = "r1"
>  PE = "2"
>  
> 
> @@ -21,7 +21,7 @@ LIB_DEPS = "virtual/libx11 libxext libxxf86vm libxdamage libxfixes libxml2-nativ
>  
>  DEPENDS = "makedepend-native flex-native bison-native ${PROTO_DEPS} ${LIB_DEPS}"
>  
> -PROVIDES = "virtual/libgl"
> +PROVIDES = "virtual/libgl virtual/libgles1 virtual/libgles2"
>  
>  # for mesa-dri and mesa-xlib
>  FILESEXTRAPATHS_append := "${THISDIR}/mesa:"
> @@ -34,6 +34,8 @@ EXTRA_OECONF = "--enable-glu \
>                  --enable-glx-tls \
>                  --enable-shared-glapi"
>  
> +PACKAGECONFIG ??= "${@base_contains('MACHINE_FEATURES', 'x86', 'gles', '', d)}"


I've taken this but could we change this to:

PACKAGECONFIG ??= ""
PACKAGECONFIG_x86 ?= "gles"

since I'd prefer to rely on the architecture override than the
MACHINE_FEATURES. This recipe shouldn't be machine specific if we can
help it.

Cheers,

Richard






  reply	other threads:[~2012-08-19 10:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:58 [PATCH 0/8] Enable EGL and GLES in x86 Mesa Ross Burton
2012-08-13 18:58 ` [PATCH 1/8] base.bbclass: fix PACKAGECONFIG handling code Ross Burton
2012-08-13 18:58 ` [PATCH 2/8] clutter: DOLT isn't used anymore Ross Burton
2012-08-17 21:04   ` Saul Wold
2012-08-13 18:58 ` [PATCH 3/8] mesa: Add a mesa-dri-glsl-native_git recipe Ross Burton
2012-08-13 18:58 ` [PATCH 4/8] mesa: enable GLES v1 and v2 Ross Burton
2012-08-19  9:51   ` Richard Purdie [this message]
2012-08-13 18:58 ` [PATCH 5/8] core: Prefer mesa-dri as virtual/libopengles1/2 provider Ross Burton
2012-08-13 18:58 ` [PATCH 6/8] mesa-demos: fix GLES2 build Ross Burton
2012-08-13 18:58 ` [PATCH 7/8] mesa: respect x11 DISTRO_FEATURE Ross Burton
2012-08-13 18:58 ` [PATCH 8/8] mesa: enable EGL, with DRM and X11 platforms Ross Burton
2012-08-15  1:22 ` [PATCH 0/8] Enable EGL and GLES in x86 Mesa Saul Wold
2012-08-15  1:30   ` Khem Raj
2012-08-15  6:56   ` Burton, Ross
2012-08-15  7:36     ` Burton, Ross
2012-08-15  9:52       ` Burton, Ross
2012-08-15 10:44   ` Burton, Ross
2012-08-20 16:05 ` Saul Wold

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=1345369877.27428.84.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