Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] Fix EGL support in qt5base
Date: Tue, 17 Sep 2013 14:35:12 +0300	[thread overview]
Message-ID: <1379417712.13187.12.camel@viko> (raw)
In-Reply-To: <1379411589-8935-1-git-send-email-jezz@sysmic.org>

Hi,

On Tue, 2013-09-17 at 11:53 +0200, J?r?me Pouiller wrote:
> +else ifeq ($(BR2_PACKAGE_GPU_VIV_BIN_MX6Q)x$(BR2_PACKAGE_XORG7),yx)
> +define QT5BASE_EXTRA_OPTIONS
> +EGLFS_PLATFORM_HOOKS_SOURCES = \
> +	$(@D)/mkspecs/devices/linux-imx6-g++/qeglfshooks_imx6.cpp   \n\
> +QMAKE_CFLAGS += -DEGL_API_FB=1                                      \n\
> +QMAKE_CXXFLAGS += -DEGL_API_FB=1                                    \n\
> +QMAKE_LIBS_OPENGL_ES2 += -lEGL -lGAL                                \n\
> +QMAKE_LIBS_OPENVG += -lEGL -lGAL                                    \n

Hardcoding device specific code in qt5base.mk is not nice; but it seems
impossible to get rid of them since qt needs a platform hook path.

I have sent a patch to the list which adds .pc files to gpu-viv-bin-mx6q
package. This helps qt5 to get needed flags; but for the platform
hook .mk file still needs to be modified.

I have also sent a bug report[1] to qt developers for another file with
hardcoded EGL flags.

[1] https://bugreports.qt-project.org/browse/QTBUG-33494

  reply	other threads:[~2013-09-17 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  7:37 [Buildroot] Fix to Qt5base-build Espen Frimann Koren
2013-09-17  9:53 ` [Buildroot] [PATCH v1] Fix EGL support in qt5base Jérôme Pouiller
2013-09-17 11:35   ` Fatih Aşıcı [this message]
2013-09-17 18:33   ` Thomas Petazzoni
2013-09-18 11:13     ` Jérôme Pouiller
2013-09-18 16:27       ` 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=1379417712.13187.12.camel@viko \
    --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