Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-kde][PATCH] qt4-x11-free 4.8.0 bbappend: fix GLES configure switch and turn it on for AM335x SoCs as well
Date: Mon, 23 Apr 2012 16:46:41 +0100	[thread overview]
Message-ID: <2199708.NNXS638hI1@helios> (raw)
In-Reply-To: <1335191135-6762-1-git-send-email-koen@dominion.thruhere.net>

On Monday 23 April 2012 16:25:35 Koen Kooi wrote:
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>  recipes-misc-support/qt4-x11-free_4.8.0.bbappend |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-misc-support/qt4-x11-free_4.8.0.bbappend
> b/recipes-misc-support/qt4-x11-free_4.8.0.bbappend index b5a3c16..4895893
> 100644
> --- a/recipes-misc-support/qt4-x11-free_4.8.0.bbappend
> +++ b/recipes-misc-support/qt4-x11-free_4.8.0.bbappend
> @@ -1,7 +1,8 @@
> -QT_GLFLAGS_omap3 = "-egl"
> +QT_GLFLAGS_omap3 = "-opengl es2 "
>  DEPENDS_append_omap3 = " libgles-omap3"
> +DEPENDS_append_ti33x = " libgles-omap3"
> 
>  # Needed by kdelibs
>  QT_DISTRO_FLAGS = "-accessibility -sm"
> 
> -PRINC := "${@int(PRINC) + 1}"
> \ No newline at end of file
> +PRINC := "${@int(PRINC) + 2}"

Can we avoid this machine-specific stuff creeping into software layers? At least 
in this case we're appending something in OE-Core so there should be no 
problem with this appearing in an append in the BSP(s).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2012-04-23 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 14:25 [meta-kde][PATCH] qt4-x11-free 4.8.0 bbappend: fix GLES configure switch and turn it on for AM335x SoCs as well Koen Kooi
2012-04-23 15:28 ` Samuel Stirtzel
2012-04-23 15:46 ` Paul Eggleton [this message]
2012-04-23 19:39   ` Koen Kooi
2012-04-23 21:16     ` Paul Eggleton
2012-04-24 13:54       ` Samuel Stirtzel
2012-04-24 14:21         ` Paul Eggleton

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=2199708.NNXS638hI1@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@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