All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Urs Fässler" <urs@bytesatwork.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
Date: Thu, 20 Feb 2014 08:50:57 +0100	[thread overview]
Message-ID: <1392882657.29514.3.camel@mars.bytesatwork.ch> (raw)
In-Reply-To: <CAP9ODKo96otJprbv_3OboT4WpiKUdXJdyKdkt6ppJK3aC+kzDg@mail.gmail.com>

On Mit, 2014-02-19 at 16:11 -0300, Otavio Salvador wrote:
> On Wed, Feb 19, 2014 at 12:22 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
> > When looking for Qt5 components and files we ought to use the Qt5
> > specific path. In case the distribution wants to have a flat tree it
> > can set QT_DIR_NAME and it will still works as expected.
> >
> > Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> > ---
> > I have built two image and the SDK from scratch using this with no
> > issues. Could someone also give this a try?
> 
> Today I rebuilt 5.2.1 image and SDK in two build machines (one Debian
> Sid and another Debian 7.4 based) and both succeed.
> 
> Did someone try this one?
> 

I successfully built Qt 5.2.1 (from the 5.2.1 repository, not the above
patch) for ARM on Debian 7.4. I had some problems with cmake stuff, but
not sure if this has to do with my configuration.


-- 
bytes at work
Konradstrasse 15
CH-8400 Winterthur
Switzerland

phone: +41 52 213 79 79
fax:   +41 52 203 27 13




  reply	other threads:[~2014-02-20  7:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  3:22 [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths Otavio Salvador
2014-02-19 19:11 ` Otavio Salvador
2014-02-20  7:50   ` Urs Fässler [this message]
2014-02-20 11:57     ` Otavio Salvador
2014-02-26 12:23       ` Urs Fässler
2014-02-20 12:18 ` Martin Jansa
2014-02-20 12:22   ` Otavio Salvador
2014-02-20 12:37     ` Otavio Salvador
2014-02-20 12:42     ` Martin Jansa
2014-02-20 12:52       ` Otavio Salvador

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=1392882657.29514.3.camel@mars.bytesatwork.ch \
    --to=urs@bytesatwork.ch \
    --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 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.