From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.
Date: Wed, 2 Jul 2014 15:36:48 -0400 [thread overview]
Message-ID: <20140702193648.GD15788@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C6DA912@DFLE08.ent.ti.com>
On Wed, Jul 02, 2014 at 03:34:38PM -0400, Cooper Jr., Franklin wrote:
>
>
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > bounces@arago-project.org] On Behalf Of Ulf Samuelsson
> > Sent: Wednesday, July 02, 2014 2:23 PM
> > To: Dmytriyenko, Denys
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
> > no OpenGL libraries, but completes after cleaning qtbase.
> >
> > 2014-07-02 21:18, Denys Dmytriyenko skrev:
> > > On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> > >> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> > >>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> > >>>
> > >>>
> > >>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> > >>>>> When I build an image with QT5 using meta-arago, qtbase fails with
> > >>>>> a lot of error messages.
> > >>>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> > >>>>> Moreover, why are you still using 5.1.1? There were many fixes in
> > >>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
> > >>>>> layers and features you configure. Either way, it's a discussion
> > >>>>> for a distro layer, you can use meta-arago mailing list for that...
> > >>>> I looked through meta-arago and meta-qt5 about a month ago for
> > compatability.
> > >>>>
> > >>>> I checked again today:
> > >>>>
> > >>>> meta-qt5/master = 5.3.0
> > >>>> meta-qt5/daisy = 5.2.1
> > >>>> meta-qt5/dora = 5.1.1
> > >>>>
> > >>>> meta-arago/master = 5.2.0
> > >>>> meta-arago/dora = 5.2.0 (used to be 5.1.1)
> > >>>> There is no meta-arago/daisy branch.
> > >>>>
> > >>>> The only revision I could find which was available in both was 5.1.1.
> > >>>> and that is why I used it.
> > >>>>
> > >>>> It would make sense if the qt5 related recipes in meta-arago matched
> > those in meta-qt5.
> > >>>>
> > >>>> Now meta-arago is using 5.2.0 which is not present in any branch of
> > >>>> meta-qt5 (did not check old branches, only dora and daisy).
> > >>>>
> > >>>> I dont understand why the meta-arago:dora recipes for qt5 has been
> > >>>> updated from 5.1.1 to 5.2.0, thus making it incompatible with meta-
> > qt5:dora. Isn't this a mistake.
> > >>> meta-qt5 for long time only had master, moreover, due to some
> > >>> requirements, we needed latest 5.2 version of qt5, which was only
> > >>> available from master and not from Dora, while meta-arago was
> > >>> generally Dora based. Since then meta-qt5 was updated to 5.2.1, and
> > >>> meta-arago has recently switched to Daisy - some cleanup is still going
> > on...
> > >>>
> > >> I think in order to clean up:
> > >> 1) meta-arago:dora should switch back to 5.1.1
> > >> 2) a daisy branch should be added to meta-arago (or daisy-devel)
> > >> using 5.2.1
> > >> 3) meta-arago:master should be 5.3.0
> > >>
> > >> 5.2.0 recipes should be deleted, or moved to an intermediate branch
> > >> (daisy-rc1?)
> > > No.
> > So whats the plan?
> > Does it make sense to have different version numbers in meta-arago, than in
> > meta-qt5?
> >
> > Is there a time schedule to have 5.2.1/5,3,0 support?
> [Franklin] The way meta-qt5 and meta-arago works is indeed different
> compared to other layers. Meta-arago master tracks meta-qt5 master.
> Meta-arago dora tracks meta-arago daisy. I think we need to properly
What? Complete nonsense!
> document this and even include it in the README file but of course work on
> daisy is still being done so it might just be on someone's short term todo
> list.
>
> Ulf,
> Are you still having issues with Qt5 support when you use meta-qt5 master?
> >
> > BR
> > Ulf Samuelsson
> >
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
next prev parent reply other threads:[~2014-07-02 19:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53B44965.5050502@emagii.com>
2014-07-02 18:05 ` [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase Ulf Samuelsson
2014-07-02 18:13 ` Denys Dmytriyenko
2014-07-02 19:13 ` Ulf Samuelsson
2014-07-02 19:18 ` Denys Dmytriyenko
2014-07-02 19:22 ` Ulf Samuelsson
2014-07-02 19:34 ` Cooper Jr., Franklin
2014-07-02 19:36 ` Denys Dmytriyenko [this message]
2014-07-02 19:42 ` Cooper Jr., Franklin
2014-07-02 19:50 ` Denys Dmytriyenko
2014-07-02 20:26 ` Ulf Samuelsson
2014-07-02 20:36 ` Cooper Jr., Franklin
2014-07-03 6:23 ` Color output (was: Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase) Ulf Samuelsson
2014-07-03 11:43 ` BBB Problem: No USB host at boot Ulf Samuelsson
2014-07-03 14:16 ` Denys Dmytriyenko
2014-07-03 17:13 ` Color output Ulf Samuelsson
2014-07-02 20:37 ` [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase Ulf Samuelsson
2014-07-02 19:34 ` Denys Dmytriyenko
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=20140702193648.GD15788@edge \
--to=denys@ti.com \
--cc=fcooper@ti.com \
--cc=meta-arago@arago-project.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.