From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] qt5webengine: enable build for 5.6.3
Date: Mon, 27 Nov 2017 21:43:39 +0100 [thread overview]
Message-ID: <20171127214339.6851dd9d@windsurf.home> (raw)
In-Reply-To: <20171123232619.29849-1-gael.portay@savoirfairelinux.com>
Hello,
On Thu, 23 Nov 2017 18:26:19 -0500, Ga?l PORTAY wrote:
> The build was broken in 5.6.2 and was disabled.
>
> It compiles fine since 5.6.3.
>
> The two additional patches are useful at run-time.
>
> The first one avoid the need to specify the path to the SSL certificate
> directory (using an additional environment variable).
>
> The second one is the same used in 5.9.x (plus resolved conflicts). It uses the
> process's context to get handles on EGL and GLESv2 libraries. Those libraries
> are linked to Qt WebEngine at compile time.
>
> The patch is particularly usefull for RPI boards since the raspberrypi userland
> package does not provide the libEGLv2.so.2 and libGLES.so.1 symlinks. Both
> library paths are hardcoded in Qt WebEngine.
>
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> ---
Following the feedback from Yann on the licensing question, I applied
to the next branch. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-27 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 23:26 [Buildroot] [PATCH v2 1/1] qt5webengine: enable build for 5.6.3 Gaël PORTAY
2017-11-24 9:04 ` Thomas Petazzoni
2017-11-25 13:02 ` Yann E. MORIN
2017-11-27 20:43 ` 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=20171127214339.6851dd9d@windsurf.home \
--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