From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12416] qt5webengine should not use WEBENGINE_CONFIG
Date: Tue, 18 Feb 2020 13:47:36 +0000 [thread overview]
Message-ID: <bug-12416-163-jaqxokya8F@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12416-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12416
--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
Thanks for the bug report and suggested patch (and sorry for the delayed
response).
Meanwhile Nathan Ford took care of the suggested patch plus missing webp mux
and alsa support ([1], [2])..., the suggested patch seems to work for the
Qt-latest/5.12.x case ([3])...
One further question out of interest, on which hardware do you run
qtwebengine and how (or which buildroot config/defconfig do you use)?
There is a report from one buildroot user not to be able to run
the minimal example on RaspberryPi Zero (see [4] and [5])...
[1] http://lists.busybox.net/pipermail/buildroot/2020-January/272066.html
[2] https://patchwork.ozlabs.org/patch/1227357/
[3] http://lists.busybox.net/pipermail/buildroot/2020-February/274385.html
[4] http://lists.busybox.net/pipermail/buildroot/2020-February/273320.html
[5] http://lists.busybox.net/pipermail/buildroot/2020-February/273329.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-02-18 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 1:56 [Buildroot] [Bug 12416] New: qt5webengine should not use WEBENGINE_CONFIG bugzilla at busybox.net
2019-12-19 8:23 ` [Buildroot] [Bug 12416] " bugzilla at busybox.net
2020-02-18 13:47 ` bugzilla at busybox.net [this message]
2020-02-20 7:27 ` bugzilla at busybox.net
2020-05-26 9:25 ` bugzilla at busybox.net
2024-06-15 14:51 ` bugzilla
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=bug-12416-163-jaqxokya8F@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox