From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt5multimedia: fix plugins videonode egl x11 header related compile failure
Date: Sun, 2 Jul 2017 00:33:32 +0200 [thread overview]
Message-ID: <20170702003332.771dd45c@windsurf> (raw)
In-Reply-To: <20170626211311.10890-1-ps.report@gmx.net>
Hello,
On Mon, 26 Jun 2017 23:13:11 +0200, Peter Seiderer wrote:
> +diff --git a/src/plugins/videonode/egl/egl.pro b/src/plugins/videonode/egl/egl.pro
> +index 7151123..08ec149 100644
> +--- a/src/plugins/videonode/egl/egl.pro
> ++++ b/src/plugins/videonode/egl/egl.pro
> +@@ -3,6 +3,9 @@ TARGET = eglvideonode
> + QT += multimedia-private qtmultimediaquicktools-private
> + CONFIG += egl
> +
> ++# Avoid X11 header collision, use generic EGL native types
> ++DEFINES += MESA_EGL_NO_X11_HEADERS
> ++
I am not really convinced by this patch. Indeed, I believe it should be
the OpenGL providers that define this constant when needed. If you look
at the config that generated the build failure you're trying to fix
(http://autobuild.buildroot.net/results/364/364a76bbf90251f9cae2abd3ef2e382758eae538),
you'll see that the OpenGL provider used is mali-t76x. However,
package/mali-t76x/glesv2.pc contains:
Cflags: -I${includedir} -DMESA_EGL_NO_X11_HEADERS
So, I would expect that Qt5 should not need to redefine it again.
Obviously, what worries me is that fixing Qt5 will fix just Qt5, and
not any other package using the same OpenGL provider.
What do you think?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-01 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 21:13 [Buildroot] [PATCH v1] qt5multimedia: fix plugins videonode egl x11 header related compile failure Peter Seiderer
2017-07-01 22:33 ` Thomas Petazzoni [this message]
2017-07-02 19:01 ` Peter Seiderer
2017-07-02 21:14 ` Thomas Petazzoni
2017-07-03 18:46 ` Peter Seiderer
2017-07-03 19:02 ` Thomas Petazzoni
2017-07-05 19:53 ` Peter Seiderer
2017-07-05 20:03 ` Thomas Petazzoni
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=20170702003332.771dd45c@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox