All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Matthew McClintock <msm@freescale.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qmake: add linux-qnuspe to the list of supported targets
Date: Thu, 06 Sep 2012 10:20:50 +0100	[thread overview]
Message-ID: <2905564.VViGOl5k8s@helios> (raw)
In-Reply-To: <1346785794-18278-1-git-send-email-msm@freescale.com>

On Tuesday 04 September 2012 14:09:54 Matthew McClintock wrote:
> Signed-off-by: Matthew McClintock <msm@freescale.com>
> ---
>  meta/classes/qmake_base.bbclass |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/qmake_base.bbclass
> b/meta/classes/qmake_base.bbclass index d1008b6..f972b27 100644
> --- a/meta/classes/qmake_base.bbclass
> +++ b/meta/classes/qmake_base.bbclass
> @@ -48,7 +48,7 @@ addtask generate_qt_config_file after do_patch before
> do_configure
> 
>  qmake_base_do_configure() {
>  	case ${QMAKESPEC} in
> -	*linux-oe-g++|*linux-uclibc-oe-g++|*linux-gnueabi-oe-g++|*linux-uclibceabi
> -oe-g++)
> +	*linux-oe-g++|*linux-uclibc-oe-g++|*linux-gnueabi-oe-g++|*linux-uclibceab
> i-oe-g++|*linux-gnuspe-oe-g++) ;;
>  	*-oe-g++)
>  		die Unsupported target ${TARGET_OS} for oe-g++ qmake spec

Oops, I missed this and created my own equivalent fix based on the file from OE-
Classic. The good news is it has been merged now though, and should support 
uClibc builds as well.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-09-06  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 19:09 [PATCH] qmake: add linux-qnuspe to the list of supported targets Matthew McClintock
2012-09-06  9:20 ` Paul Eggleton [this message]
2012-09-06 16:20   ` McClintock Matthew-B29882

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=2905564.VViGOl5k8s@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=msm@freescale.com \
    --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 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.