All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] qt5: add mx5 and mx6 support
Date: Fri, 31 May 2013 16:15:56 +0200	[thread overview]
Message-ID: <20130531161556.5c06374b@e6520eb> (raw)
In-Reply-To: <CAP9ODKoh2_+7oZ=U+pWbiTcxDXr-+FkYdGX8ZGwy3PvUr3nCqQ@mail.gmail.com>

Le Fri, 31 May 2013 10:18:44 -0300,
Otavio Salvador <otavio@ossystems.com.br> a écrit :

> On Wed, May 29, 2013 at 3:04 PM, Eric Bénard <eric@eukrea.com> wrote:
> 
> > - this allow to build qt5 with OpenGL ES support for i.MX5 and i.MX6
> > - tested on i.MX51, i.MX53 and i.MX6Q
> >
> > Signed-off-by: Eric Bénard <eric@eukrea.com>
> >
> 
> ...
> 
> 
> >  recipes-qt/qt5/qtbase/mx5/qeglfshooks_imx5.cpp |  105
> > ++++++++++++++++++++++++
> >  recipes-qt/qt5/qtbase_5.0.2.bbappend           |   68 +++++++++++++++
> >
> 
> ...
> 
> Thinking more about it, I think we should put these inside a meta-qt5
> directory so we know what will be 'included'. Otherwse we may need to pick
> every file depending on each layer and it might be difficult to understand
> what is in use and what is not.
> 
please apply as is and create a patch on top of it to achieve the
organization you prefer.

Eric


  reply	other threads:[~2013-05-31 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 18:04 [meta-fsl-arm][PATCH] qt5: add mx5 and mx6 support Eric Bénard
2013-05-31 13:18 ` Otavio Salvador
2013-05-31 14:15   ` Eric Bénard [this message]
2013-05-31 15:00     ` Otavio Salvador
2013-05-31 15:02       ` Eric Bénard
2013-05-31 15:04         ` Otavio Salvador
2013-05-31 15:35           ` Eric Bénard
2013-05-31 16:23             ` Otavio Salvador
2013-05-31 20:06               ` Eric Bénard
2013-05-31 20:30                 ` 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=20130531161556.5c06374b@e6520eb \
    --to=eric@eukrea.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.