All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Sundareson, Prabindh" <prabu@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: meta-ti + meta-qt5
Date: Thu, 20 Jun 2013 01:52:26 -0400	[thread overview]
Message-ID: <20130620055226.GS13356@edge> (raw)
In-Reply-To: <321768C95D21724485BCE784F1BE98473EB53340@DBDE04.ent.ti.com>

On Thu, Jun 20, 2013 at 01:03:04AM -0400, Sundareson, Prabindh wrote:
> I have validated libgles-omap3 on the AMSDK 5.07 build configuration (that 
> does not have X11 enabled), so what you faced may be a different issue on 
> the libgles front.

Correct, becasue your patches were missing the actual x11 recipe, which I had 
to add - see my other email earlier. :)  But I agree - it's a slightly 
different issue.


> I would wait for the verbose log from Nicolas for the qt5 issue he faced,
> 
> regards,
> Prabu
> 
> 
> -----Original Message-----
> From: Dmytriyenko, Denys 
> Sent: Thursday, June 20, 2013 10:25 AM
> To: Nicolas Dechesne
> Cc: Sundareson, Prabindh; meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] meta-ti + meta-qt5
> 
> On Thu, Jun 20, 2013 at 12:46:21AM -0400, Nicolas Dechesne wrote:
> > On Thu, Jun 20, 2013 at 12:34 AM, Sundareson, Prabindh <prabu@ti.com> wrote:
> > 
> > > The instructions build eglfs as well (without xcb), as in the below patch.
> > > Just that I cannot test it on platform due to the absence of GLES2 driver.
> > >  verbose flag in the qt configuration (qt5.inc) would help debug 
> > > what is going wrong.****
> > >
> > > ** **
> > >
> > >
> > > https://github.com/prabindh/meta-qt5/commit/c8129fb5057f9254c773f82d
> > > 2fdbd85d9c56410a
> > > ****
> > >
> > >
> > yeah, i am using something similar *but* i do not have x11 in 
> > DISTRO_FEATURES, and i suspect you might have it, right? without X11 
> > feature, the x11 -dev packages are pulled/installed, and then the 
> > qtbase configure script will fail to 'check' for EGL.
> 
> Heh, I was having similar issues with Prabu's recent libgles-omap3 patches. 
> It would try to pull x11 packages due to -dev dependencies and complain that 
> DISTRO_FEATURES lacks X11 setting... It's not exactly the same issue, but 
> seems related.
> 
> --
> Denys


  reply	other threads:[~2013-06-20  5:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  2:04 meta-ti + meta-qt5 Nicolas Dechesne
2013-06-20  2:09 ` Sundareson, Prabindh
2013-06-20  2:16   ` Denys Dmytriyenko
2013-06-20  2:45     ` Sundareson, Prabindh
2013-06-20  2:38   ` Nicolas Dechesne
2013-06-20  3:01     ` Sundareson, Prabindh
2013-06-20  4:14       ` Nicolas Dechesne
2013-06-20  4:34         ` Sundareson, Prabindh
2013-06-20  4:46           ` Nicolas Dechesne
2013-06-20  4:55             ` Denys Dmytriyenko
2013-06-20  5:03               ` Sundareson, Prabindh
2013-06-20  5:52                 ` Denys Dmytriyenko [this message]
2013-06-21  4:50                 ` Nicolas Dechesne
2013-06-21  7:49                   ` Sundareson, Prabindh
2013-06-24 20:19                     ` Nicolas Dechesne
2013-06-25  1:15                       ` Sundareson, Prabindh
2013-06-20  2:15 ` Denys Dmytriyenko
2013-06-20  5:27 ` Richard Röjfors

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=20130620055226.GS13356@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=prabu@ti.com \
    /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.