From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-08-02
Date: Thu, 3 Aug 2017 20:07:41 +0200 [thread overview]
Message-ID: <20170803200741.245f3b6f@windsurf.lan> (raw)
In-Reply-To: <a8c9e92b-38f9-88c2-c423-99f946fa5571@microchip.com>
Hello,
On Thu, 3 Aug 2017 10:30:59 -0700, Joshua Henderson wrote:
> For reference, I opened an upstream Qt bug [1] about this. This build log is
> not strictly identical, but looks to be the same problem. I believe the
> issue is gtk3 is properly auto detected by Qt build in order to build an
> optional Qt gtk3 plugin, but what it really needs is gtk3 compiled with X11.
> So, when gtk3 is built without X11 in buildroot, the Qt build fails.
>
> Any direction on whether this should be solved:
> 1) in buildroot as config/build dependency (seems odd to make a dependency on
> X11 for qt5base if gtk3 is enabled),
> 2) patch Qt,
> 3) by explicitly disabling building gtk3 theme support in qt5base (instead of
> being automatic),
> 4) with some combination of the above.
I would say a combination of (1) and (3).
We want to:
* Enable the gtk3 theme support only when the necessary dependencies
are met. In this case, it would be BR2_PACKAGE_LIBGTK3_X11, which
indicates that gtk3 is enabled with its X11 backend.
* Be explicit about enabling and disabling the gtk3 theme. I.e
explicitly enable it when BR2_PACKAGE_LIBGTK3_X11=y, explicitly
disable it otherwise.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-03 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-08-02 Thomas Petazzoni
2017-08-03 17:30 ` Joshua Henderson
2017-08-03 18:07 ` Thomas Petazzoni [this message]
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=20170803200741.245f3b6f@windsurf.lan \
--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