[wpe-webkit] AArch64 builds in AUR

Andrea Giammarchi andrea.giammarchi at gmail.com
Wed Mar 6 04:44:43 PST 2019

Unless the direct backend is notably faster, I think I'm fine with Wayland,
also because I believe you need some compositor when you open, as example,
the files explorer, so GTK on Weston would be just fine, right?

Last question about the canvas:

> Note that even with ENABLE_ACCELERATED_2D_CANVAS disabled, WebGL is
always rendered by the GPU.

One of the demo used in the WPE on Pi post benchmarks the canvas
https://smashcat.org/av/canvas_test/ and I've seen it with my eyes it's
indeed blazing fast compared to the regular canvas. I don't think it uses
WebGL though, so I wonder if I am missing anything.

So, how would I force-enable that ?

On Wed, Mar 6, 2019 at 1:30 PM Adrian Perez de Castro <aperez at igalia.com>

> Hello Andrea,
> On Wed, 6 Mar 2019 12:38:54 +0100, Andrea Giammarchi <
> andrea.giammarchi at gmail.com> wrote:
> > Crickets so far ... btw, I'm going skiing for the Weekend so I'll try to
> > build WPE directly on the Pi.
> >
> > Everything seems to work fine except ENABLE_ACCELERATED_2D_CANVAS AND
> > ENABLE_ENCRYPTED_MEDIA are both OFF, while all others are ON.
> >
> > I am interested specially in the ENABLE_ACCELERATED_2D_CANVAS, why
> wouldn't
> > that work?
> ENABLE_ACCELERATED_2D_CANVAS is disabled by default because it uses
> Cairo-GL,
> which does not really work as well as you may imagine, and can be slower in
> some cases depending on many factors (including, but not limited to, the
> being used). YMMV.
> Note that even with ENABLE_ACCELERATED_2D_CANVAS disabled, WebGL is always
> rendered by the GPU.
> > Also I have another question: is wpebackend preferred over
> wpebackend-fdo ?
> > Latter seems for Wayland, which I'm OK with, but not sure it performs any
> > better than the former.
> The “wpebackend” package is deprecated and has been replaced by “libwpe”
> (the name was confusing, because “wpebackend” was not a backend: it was
> just a library used to implement and use backends).
> An alternative WPE backend that works for the Raspberry Pi is the RDK
> backend
> [1] when built passing “-DUSE_BACKEND_BCM_RPI=ON” to CMake.
> Note that I have not been using the RDK backend myself so I cannot comment
> on
> its status, and that's the reason why I have not submitted an AUR package
> for
> it — but should work, with the advantage that a Wayland compositor is not
> needed, but with the limitations that only one Web view can be created, and
> that it uses the 32-bit Raspberry Pi userland libraries (which cannot be
> built
> in 64-bit mode [2]).
> > Thanks again for extra clarifications.
> Happy to help :)
> -Adrián
> ---
> [1] https://github.com/WebPlatformForEmbedded/WPEBackend-rdk
> [2] https://github.com/raspberrypi/userland/issues/314
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-wpe/attachments/20190306/0cfbe99c/attachment.html>

More information about the webkit-wpe mailing list