From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] qt5base: fix build when egl headers need a definition
Date: Wed, 18 Sep 2013 20:52:22 +0300 [thread overview]
Message-ID: <201309182052.22917.fatih.asici@gmail.com> (raw)
The build with gpu-viv-bin-mx6q libraries was broken since it wasn't
using "-DEGL_API_FB=1" flag which is found in egl.pc.
Signed-off-by: Fatih A??c? <fatih.asici@gmail.com>
---
Changes v1 -> v2:
- Add description and Signed-off-by line to the patch (suggested by
Thomas Petazzoni)
package/qt5/qt5base/qt5base-egl-cflags.patch | 28
++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 package/qt5/qt5base/qt5base-egl-cflags.patch
diff --git a/package/qt5/qt5base/qt5base-egl-cflags.patch
b/package/qt5/qt5base/qt5base-egl-cflags.patch
new file mode 100644
index 0000000..a483997
--- /dev/null
+++ b/package/qt5/qt5base/qt5base-egl-cflags.patch
@@ -0,0 +1,28 @@
+egl.prf: Append egl CFLAGS to QMAKE_C[XX]FLAGS
+
+Projects including egl in their config (e.g. with CONFIG += egl) cannot get
+egl CFLAGS without this.
+
+Signed-off-by: Fatih A??c? <fatih.asici@gmail.com>
+
+--- a/configure
++++ b/configure
+@@ -5391,6 +5391,7 @@
+ QMAKE_CFLAGS_EGL=`$PKG_CONFIG --cflags egl 2>/dev/null`
+ QMakeVar set QMAKE_INCDIR_EGL "$QMAKE_INCDIR_EGL"
+ QMakeVar set QMAKE_LIBS_EGL "$QMAKE_LIBS_EGL"
++ QMakeVar set QMAKE_CFLAGS_EGL "$QMAKE_CFLAGS_EGL"
+ fi # detect EGL support
+ if compileTest qpa/egl "EGL" $QMAKE_CFLAGS_EGL $QMAKE_LIBS_EGL; then
+ CFG_EGL=yes
+--- a/mkspecs/features/egl.prf
++++ b/mkspecs/features/egl.prf
+@@ -14,6 +14,8 @@
+ } else {
+ INCLUDEPATH += $$QMAKE_INCDIR_EGL
+ LIBS_PRIVATE += $$QMAKE_LIBS_EGL
++ QMAKE_CFLAGS += $$QMAKE_CFLAGS_EGL
++ QMAKE_CXXFLAGS += $$QMAKE_CFLAGS_EGL
+ LIBS += $$QMAKE_LFLAGS_EGL
+ for(p, QMAKE_LIBDIR_EGL) {
+ exists($$p):LIBS_PRIVATE += -L$$p
--
1.7.10.4
reply other threads:[~2013-09-18 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201309182052.22917.fatih.asici@gmail.com \
--to=fatih.asici@gmail.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