>
> So https://gerrit.libreoffice.org/#/c/31465/ is the patch to move
> libgltf from glew to libepoxy. If we can get that in first, then we can
> require libgltf >= 0.1.0 rather than 0.0.0 to head off system-libgltf
> incompatibilities
>
Or, we could, dare I say it, conclude that this gltf and
On Tue, 2016-11-29 at 14:48 +0100, Markus Mohrhard wrote:
> Sadly I don't recall why I chose glew instead of libepoxy back then.
> However looking at it now it seems like libepoxy is the smarter
> choice as long as it works correctly on Mac.
>
> For gltf as we control the code we can of course
Hi Caolan,
On 29/11/16 12:20, Caolán McNamara wrote:
> locally I have our opengl slideshow transitions working[1] under gtk3
> on wayland and I'd like to merge this to master.
Nice work =)
> Is there any objection to the principle of dropping glew in favour of
> epoxy, or do I need to
Hi,
On Tue, Nov 29, 2016 at 1:20 PM, Caolán McNamara wrote:
> locally I have our opengl slideshow transitions working[1] under gtk3
> on wayland and I'd like to merge this to master. The gtk3 part is
> fairly trivial as it turns out. But glew doesn't work under wayland.
>
Hey,
On Tue, Nov 29, 2016 at 1:20 PM, Caolán McNamara wrote:
> locally I have our opengl slideshow transitions working[1] under gtk3
> on wayland and I'd like to merge this to master. The gtk3 part is
> fairly trivial as it turns out. But glew doesn't work under wayland.
>
locally I have our opengl slideshow transitions working[1] under gtk3
on wayland and I'd like to merge this to master. The gtk3 part is
fairly trivial as it turns out. But glew doesn't work under wayland.
epoxy does however (and it's what gtk3 itself uses). epoxy claims to
support all of our