[wpe-webkit] AArch64 builds in AUR
Adrian Perez de Castro
aperez at igalia.com
Wed Mar 27 07:14:16 PDT 2019
I was busy getting the 2.24.0 release out, among other things. I will try
now to give you some answers — sorry about the delay ~_~
On Sun, 17 Mar 2019 14:29:00 +0100, Andrea Giammarchi <andrea.giammarchi at gmail.com> wrote:
> Sorry for the late reply (I was without my PC/RPi3 this week)
> The good news is that somehow I managed to see something ... however, if I
> start Weston fullscreen it crashes, every single time.
> If I specify width, height of 1280x720 it crashes.
> If I say nothing but --socket=wpe and then I cog duckduckgo it shows a
> 1024x1024 duckduckgo experience, with no mouse showing up whatsoever, but
> promising 10FPS on WebGL Aquarium at that resolution and 500 fishes.
> The list of ugly bits I've not mentioned yet is here:
> 1. cog and cog-git requires wpewebkit ... building that package is a
> lottery. I'd be awesome to have a cog that doesn't strictly need wpewebkit
> and assumes it's already installed
This should be fine as long as your “wpewebkit-aarch64” package includes a
couple of lines like the following in its PKGBUILD:
The second line is needed to ensure that either package is installed, but
not both at the same time, because they would include the same set of files,
which is something Pacman will notice and report as an error.
Of course, the binary package also needs to include the development headers
and other auxiliary files (like the “.pc” files for pkg-config) in order to be
able to build other packages which depend on “wpewebkit”.
> 2. TinyWL builds and shows nothing. A grayish full screen (1080p)
> without duckduckgo in it. I am running from the terminal without any Weston
> session ever started. Not sure how to help debugging this
Do not forget to pass to the TinyWL command line invocation the program that
it will run at startup. I am not 100% sure, but I think it only takes one
parameters, so if your command has parameters itself (which is Cog's case,
to pass “--platform=fdo” and so on), then the easiest way would be to use
a small script:
% cat <<EOF > tinywl-run-cog
exec /usr/bin/cog --platform=fdo https://duckduckgo.com
% chmod +x tinywl-run-cog
% tinywl -s ./tinywl-run-cog
> 3. however, since TinyWL is nowhere in AUR, I prefer using ArchLinux
> bricks so ... Weston is just fine. I'm using a weston.ini and beside the
> resolution gotcha, everything seems to work OK
Weston is known to work well, so it's a safe bet :-)
> 4. for some reason, my PC cannot build WPEWebKit anymore. It always
> fails at the last 111 files. I might have messed up something but ...
Ouch. If you can share a build log in some kind of pastebin, maybe I can
take a quick look in case it may be easy to troubleshoot.
> 5. there is a cairo-git that --enable-gl already, and I might use that
> one, but I believe it should also --enable-glesv2 ... is that correct?
Yes. In WPE WebKit we use GLESv2 only, because that is the GL implementation
that is available in most embedded platforms, and is also provided by Mesa.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: not available
More information about the webkit-wpe