From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure with Vivante and QT5 w/ eglfs
Date: Fri, 4 Mar 2016 14:43:56 +0100 [thread overview]
Message-ID: <20160304144356.4f463489@free-electrons.com> (raw)
In-Reply-To: <CAAMH-ytxJVmVc_D0aREVisnsU-UPX1-po6WtX4HYHz85XOA+Wg@mail.gmail.com>
Gary,
On Fri, 4 Mar 2016 14:35:55 +0100, Gary Bisson wrote:
> >> Well if we are allowed to modify qtbase I guess it would be way
> >> easier. Would something like this be acceptable?
> >> index 64a7f65..aa54b3e 100644
> >> --- a/package/qt5/qt5base/Config.in
> >> +++ b/package/qt5/qt5base/Config.in
> >> @@ -201,10 +201,14 @@ config BR2_PACKAGE_QT5BASE_EGLFS
> >> select BR2_PACKAGE_QT5BASE_OPENGL
> >> depends on BR2_PACKAGE_HAS_LIBEGL
> >> depends on BR2_PACKAGE_QT5_GL_AVAILABLE
> >> + depends on !BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_X11
> >>
> >> comment "eglfs backend available if OpenGL and EGL are enabled"
> >> depends on !BR2_PACKAGE_HAS_LIBEGL || !BR2_PACKAGE_QT5_GL_AVAILABLE
> >>
> >> +comment "eglfs backend not available for X11 version of i.MX 3D libraries"
> >> + depends on BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_X11
> >> +
> >
> > No this is not good, because there are other OpenGL implementations
> > than imx-gpu-viv. So at the very least, you would need something like
> > the below. I also believe it makes more sense to use positive
> > condition, i.e express a dependency on the FB output, rather than a
> > dependency on not having the X11 output.
> >
> > # If the imx-gpu-viv implementation is used, we need its FB variant
> > depends on !BR2_PACKAGE_IMX_GPU_VIV || BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_FB
> >
> > comment "eglfs backend needs the FB output of i.MX GPU libraries"
> > depends on BR2_PACKAGE_IMX_GPU_VIV && !BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_FB
>
> I agree using the positive condition is better. However I'm not sure
> to understand why !BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_X11 wouldn't work
> with other OpenGL implementations. This variable is only set when
> selecting the vivante package + x11 output. So for any other
> implementation it wouldn't be set. It's just out of curiosity that I'd
> like to understand the difference.
Aah, yes, you're right. Your version is functionally equivalent to mine.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-04 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 9:55 [Buildroot] Build failure with Vivante and QT5 w/ eglfs Antoine Tenart
2016-03-04 11:02 ` Gary Bisson
2016-03-04 11:13 ` Thomas Petazzoni
2016-03-04 13:10 ` Gary Bisson
2016-03-04 13:19 ` Thomas Petazzoni
2016-03-04 13:35 ` Gary Bisson
2016-03-04 13:43 ` Thomas Petazzoni [this message]
2016-03-04 13:50 ` Antoine Tenart
2016-03-04 13:58 ` Gary Bisson
2016-03-07 10:18 ` Antoine Tenart
2016-03-07 10:38 ` Gary Bisson
2016-03-04 14:45 ` Jérôme Pouiller
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=20160304144356.4f463489@free-electrons.com \
--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