All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] qt4: fix generated sdk
Date: Fri, 16 Sep 2011 14:09:45 -0300	[thread overview]
Message-ID: <CAP9ODKqMuGzcwz=fBWnLU+zx9rSCCk0fus=pbXwye1hjRH_wFg@mail.gmail.com> (raw)
In-Reply-To: <1316192238.20858.45.camel@ted>

On Fri, Sep 16, 2011 at 13:57, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2011-09-13 at 16:44 +0200, Eric Bénard wrote:
>> - qt4-tools-nativesdk : actually the qmake binary which gets installed
>> comes from the native recipe. This patch fix this problem by laucnhing
>> configure twice : once to compile qmake using the right toolchain for
>> nativesdk, and a second time using the native qmake to compile all the
>> other tools for the nativesdk. Then we install the right qmake.
>
> I was reading through this and wondered why we can't this use the qmake
> from the qt4-tools-native recipe?

With mine qt.conf patch (not yet sent) this ought to work fine.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



  reply	other threads:[~2011-09-16 17:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10  9:25 [PATCH] qt4: fix generated sdk Eric Bénard
2011-09-10  9:56 ` Otavio Salvador
2011-09-10  9:59   ` Eric Bénard
2011-09-10 10:03     ` Otavio Salvador
2011-09-10 10:31       ` Otavio Salvador
2011-09-13  5:44         ` Eric Bénard
2011-09-13 14:12           ` Otavio Salvador
2011-09-13 14:44             ` [PATCH v2] " Eric Bénard
2011-09-16 16:57               ` Richard Purdie
2011-09-16 17:09                 ` Otavio Salvador [this message]
2011-09-16 19:52                 ` Eric Bénard
2011-09-13 17:25           ` [PATCH] " 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='CAP9ODKqMuGzcwz=fBWnLU+zx9rSCCk0fus=pbXwye1hjRH_wFg@mail.gmail.com' \
    --to=otavio@ossystems.com.br \
    --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.