From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-01-21
Date: Tue, 23 Jan 2018 15:21:43 +0000 [thread overview]
Message-ID: <20180123152143.GD14919@momiji> (raw)
In-Reply-To: <20180122070014.D5074206F0@mail.free-electrons.com>
Hi,
On Mon, 22 Jan 2018 08:00:14 +0100 (CET), Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> x86_64 | webkitgtk-2.18.5 | NOK | http://autobuild.buildroot.net/results/57b77520d3a3fcfa683406e223771d0ccf8733df |
The configuration used for this build has an EGL provider but both OpenGL and
OpenGL ES are disabled:
- BR2_PACKAGE_HAS_LIBEGL is chosen.
- Both BR2_PACKAGE_HAS_LIBGL and BR2_PACKAGE_HAS_LIBGLES are undefined.
It seems to me that the CMake build files for WebKit should disable all the
OpenGL support if EGL is found but a GL/GLES implementation is not found.
I have filed a bug upstream to look into that:
https://bugs.webkit.org/show_bug.cgi?id=181986
In the meantime, I'll make a patch for checking in the Buildroot package
whether an OpenGL(ES) implementation is being built, and if not pass the
needed build flags to CMake in order to disable using OpenGL(ES) even if
EGL is present.
Cheers,
--
Adri?n ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180123/3446eca4/attachment.asc>
next prev parent reply other threads:[~2018-01-23 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-01-21 Thomas Petazzoni
2018-01-23 15:21 ` Adrian Perez de Castro [this message]
2018-01-24 7:59 ` Peter Korsgaard
2018-01-25 21:03 ` Adrian Perez de Castro
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=20180123152143.GD14919@momiji \
--to=aperez@igalia.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