From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig)
Date: Thu, 6 Apr 2017 18:33:16 +0200 [thread overview]
Message-ID: <20170406183316.44d8db5a@free-electrons.com> (raw)
In-Reply-To: <trinity-0603182d-d77d-4e0a-bdd1-589503badbe3-1491479231018@3capp-gmx-bs68>
Hello,
On Thu, 6 Apr 2017 13:47:11 +0200, Peter Seiderer wrote:
> Untested but maybe the following works:
>
> diff --git a/package/qt5/qt5declarative/Config.in b/package/qt5/qt5declarative/Config.in
> index 853322c..5e0fbe2 100644
> --- a/package/qt5/qt5declarative/Config.in
> +++ b/package/qt5/qt5declarative/Config.in
> @@ -3,6 +3,7 @@ config BR2_PACKAGE_QT5DECLARATIVE
> select BR2_PACKAGE_QT5XMLPATTERNS
> select BR2_PACKAGE_QT5BASE
> select BR2_PACKAGE_QT5BASE_GUI
> + select BR2_PACKAGE_QT5BASE_WIDGETS if BR2_PACKAGE_QT5BASE_EXAMPLES
> depends on BR2_PACKAGE_QT5_JSCORE_AVAILABLE
> help
> Qt is a cross-platform application and UI framework for
Thanks, can you submit as a proper patch?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-06 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 10:57 [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig) Arnout Vandecappelle
2017-04-06 11:47 ` Peter Seiderer
2017-04-06 16:12 ` Michael Nazzareno Trimarchi
2017-04-06 16:32 ` Thomas Petazzoni
2017-04-06 16:57 ` Thomas Petazzoni
2017-04-07 7:54 ` Michael Trimarchi
2017-04-07 8:06 ` Thomas Petazzoni
2017-04-07 8:09 ` Michael Trimarchi
2017-04-07 8:19 ` Thomas Petazzoni
2017-04-06 21:27 ` txt.file
2017-04-07 7:28 ` Michael Nazzareno Trimarchi
2017-04-06 16:33 ` Thomas Petazzoni [this message]
2017-04-07 18:47 ` 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=20170406183316.44d8db5a@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