From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/qt5/qt5base: examples depend on OpenGL
Date: Mon, 7 Aug 2017 18:41:49 +0200 [thread overview]
Message-ID: <20170807184149.62292a88@gmx.net> (raw)
In-Reply-To: <20170807070344.29750-1-bernd.kuhls@t-online.de>
Hello Bernd,
On Mon, 7 Aug 2017 09:03:44 +0200, Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Fixes
> http://autobuild.buildroot.net/results/001/001bc930014fca8c2a8b7a390350b4e1a15fa375/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/qt5/qt5base/Config.in | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/package/qt5/qt5base/Config.in b/package/qt5/qt5base/Config.in
> index f5de27228..f0138a10f 100644
> --- a/package/qt5/qt5base/Config.in
> +++ b/package/qt5/qt5base/Config.in
> @@ -44,11 +44,15 @@ config BR2_PACKAGE_QT5BASE_CONFIG_FILE
>
> config BR2_PACKAGE_QT5BASE_EXAMPLES
> bool "Compile and install examples (with code)"
> + depends on BR2_PACKAGE_QT5_GL_AVAILABLE
Did not (yet) look at the details, but disabling all examples (mind that all sub
modules use BR2_PACKAGE_QT5BASE_EXAMPLES) because of one failing one seems a bit
over-reacted....better solution would be to disable only the failing one, see
e.g. package/qt5/qt5declarative/0002-examples-qquickviewcomparison-and-quickwidget-needs-.patch
Regards,
Peter
> select BR2_PACKAGE_QT5BASE_NETWORK
> select BR2_PACKAGE_QT5BASE_XML
> help
> If unsure, say N.
>
> +comment "Examples need an OpenGL-capable backend"
> + depends on !BR2_PACKAGE_QT5_GL_AVAILABLE
> +
> config BR2_PACKAGE_QT5BASE_NETWORK
> def_bool y
>
next prev parent reply other threads:[~2017-08-07 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 7:03 [Buildroot] [PATCH 1/1] package/qt5/qt5base: examples depend on OpenGL Bernd Kuhls
2017-08-07 16:41 ` Peter Seiderer [this message]
2017-08-07 21:18 ` Peter Seiderer
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=20170807184149.62292a88@gmx.net \
--to=ps.report@gmx.net \
--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 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.