From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 0/3] Qt WebEngine support
Date: Sat, 12 Aug 2017 18:29:59 +0200 [thread overview]
Message-ID: <20170812182959.33997316@windsurf> (raw)
In-Reply-To: <8c8fd01f-12eb-f91f-2316-294286a2f5aa@mind.be>
Hello,
On Sat, 12 Aug 2017 17:12:37 +0200, Arnout Vandecappelle wrote:
> > BTW, it seems this bug is quite new in Qt; it appeared since QtWebengine 5.9 [2]
> > and [3].
> >
> > I will check if it requirement to build Qt WebEngine.
>
> Since adding Qt WebEngine to Buildroot is long overdue, I propose to apply it
> with the BR2_HOSTARCH_NEEDS_IA32_COMPILER work-around and resolve this issue later.
Yes, that's fine with me, provided we have a comment on top of this
select BR2_HOSTARCH_NEEDS_IA32_COMPILER that explains the situation.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-12 16:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 1:33 [Buildroot] [PATCH v6 0/3] Qt WebEngine support Gaël PORTAY
2017-08-11 1:33 ` [Buildroot] [PATCH v6 1/3] rpi-userland: fix opengl library symlinks Gaël PORTAY
2017-08-12 15:31 ` Arnout Vandecappelle
2017-08-12 15:54 ` Gaël PORTAY
2017-08-11 1:33 ` [Buildroot] [PATCH v6 2/3] qt5webengine: new package Gaël PORTAY
2017-08-11 1:33 ` [Buildroot] [PATCH v6 3/3] configs: new raspberrypi3 qt5 config Gaël PORTAY
2017-08-11 10:56 ` [Buildroot] [PATCH v6 0/3] Qt WebEngine support Zoltan Gyarmati
2017-08-11 19:29 ` Björn Kirchner
2017-08-11 20:30 ` Thomas Petazzoni
2017-08-11 22:24 ` Gaël PORTAY
2017-08-12 7:48 ` Björn Kirchner
2017-08-12 7:57 ` Thomas Petazzoni
2017-08-12 15:08 ` Gaël PORTAY
2017-08-12 15:12 ` Arnout Vandecappelle
2017-08-12 15:46 ` Gaël PORTAY
2017-08-12 20:55 ` Arnout Vandecappelle
2017-08-12 16:29 ` Thomas Petazzoni [this message]
2017-08-12 16:34 ` Gaël PORTAY
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=20170812182959.33997316@windsurf \
--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 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.