hi;
I'd like to point out that this is a build-time requirement for
libepoxy only: if the app does not use GLX on the Apple X server, then
the GLX code is never even loaded.
it'd be nice to have a libepoxy build that does not require X11 on
MacOS, but that would make it harder to have applications linking
against libepoxy run on the X server on that platform. whether or not
that is a long term strategy is a discussion worth having with Eric.
On 19 November 2014 08:10, Jasper St. Pierre <jstpierre mecheye net> wrote:
> Yeah, this is an unfortunate bug with libepoxy right now. There's a PR on
> GitHub if you want to see if that fixes it.
>
> https://github.com/anholt/libepoxy/pull/28
> All we can do is pressure Eric Anholt to merge it at this point.
>
> On Wed, Nov 19, 2014 at 12:03 AM, Philip Chimento
> <philip chimento gmail com> wrote:
>>
>> On Sun, Nov 16, 2014 at 6:32 AM, Emmanuele Bassi <ebassi gmail com> wrote:
>>>
>>> hi all;
>>>
>>> I posted this on my blog, which is syndacated on Planet GNOME, but I
>>> thought about trying to reach out to more people by using the GTK+
>>> mailing list as well.
>>>
>>> GTK+ 3.16 will have OpenGL support out of the box — at least on X11 and
>>> Wayland.
>>>
>>> if you are using GTK+ 3.x on Windows and/or MacOS X, or if you're
>>> using external libraries like GtkGLExt and GtkGLArea with GTK+ 2.x or
>>> 3.x, then I'm asking you to help out with patches and testing the
>>> OpenGL support in the master branch of GTK+. we'd really like to have
>>> OpenGL support working on all the major backends in GDK by the time we
>>> release GTK+ 3.16.0, next February.
>>
>>
>> I've started trying to build GTK master on OSX; looks like libepoxy is now
>> a dependency of GDK, and libepoxy in turn needs X11.h. How hard is that
>> dependency? It seems to me that I shouldn't need X11 for the Quartz backend.