All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH] qtbase: typo about virtual/egl depends
Date: Thu, 20 Jun 2013 08:15:20 +0200	[thread overview]
Message-ID: <51C29DF8.70901@pseudoterminal.org> (raw)
In-Reply-To: <1371700482-12885-1-git-send-email-nicolas.dechesne@linaro.org>

On 2013-06-20 05:54, Nicolas Dechesne wrote:
> The proper 'virtual' name for EGL is virtual/egl, not virtual/libegl,
> as per meta/recipes-graphics/mesa/mesa-common.inc.
>
> Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
> ---
>   recipes-qt/qt5/qtbase.inc | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-qt/qt5/qtbase.inc b/recipes-qt/qt5/qtbase.inc
> index 569332e..ee4094b 100644
> --- a/recipes-qt/qt5/qtbase.inc
> +++ b/recipes-qt/qt5/qtbase.inc
> @@ -41,7 +41,7 @@ QT_DISTRO_FLAGS_linuxstdbase = "-sm"
>   QT_SQL_DRIVER_FLAGS ?= "-no-sql-ibase -no-sql-mysql -no-sql-psql -no-sql-odbc -plugin-sql-sqlite"
>   
>   # if you want to enable egl/gles2 in your .bbappend, don't forget to add right dependencies, e.g.
> -# GL_DEPENDS = "virtual/libgles2 virtual/libegl"
> +# GL_DEPENDS = "virtual/libgles2 virtual/egl"
>   # QT_GLFLAGS = "-opengl es2 -eglfs"
>   GL_DEPENDS ?= "virtual/libgl"
>   QT_GLFLAGS ?= "-opengl"

This highlights a problem I've noticed in the past. A directory of 
officially defined virtual names would be helpful. Also, since many BSPs 
offer hardware-accelerated OpenVG, a virtual/openvg name would be 
useful. ("vg" and "libvg" are very uncommon, so I'd pick "openvg".)


      reply	other threads:[~2013-06-20  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  3:54 [meta-qt5][PATCH] qtbase: typo about virtual/egl depends Nicolas Dechesne
2013-06-20  6:15 ` Carlos Rafael Giani [this message]

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=51C29DF8.70901@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --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.