Re: help wanted for implementing GdkGLContext on Windows and MacOS X
On Wed, Nov 19, 2014 at 3:10 AM, Jasper St. Pierre 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. > We can also add the patch to continuous and jhbuild if that helps. ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: help wanted for implementing GdkGLContext on Windows and MacOS X
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. ciao, Emmanuele. On 19 November 2014 08:10, Jasper St. Pierre 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 > wrote: >> >> On Sun, Nov 16, 2014 at 6:32 AM, Emmanuele Bassi 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. >> -- >> Philip >> >> ___ >> gtk-devel-list mailing list >> gtk-devel-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/gtk-devel-list >> > > > > -- > Jasper -- http://www.bassi.io [@] ebassi [@gmail.com] ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
[PATCH] gmacros.h: Don't use __alloc_size__ with clang
It doesnt's support it yet. Add a clang feature check in case it gets added later. Signed-off-by: Lubomir Rintel --- glib/gmacros.h | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/glib/gmacros.h b/glib/gmacros.h index 0bdfa55..893707a 100644 --- a/glib/gmacros.h +++ b/glib/gmacros.h @@ -47,6 +47,13 @@ #define G_GNUC_EXTENSION #endif +/* clang feature checks. Sadly, clang masquerades as GCC even without + * a sensible feature parity. + */ +#if !defined (__has_builtin) +#define __has_builtin(builtin) 0 +#endif + /* Provide macros to feature the GCC function attribute. */ #if__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 96) @@ -63,7 +70,7 @@ #define G_GNUC_NULL_TERMINATED #endif -#if (__GNUC__ > 4) || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3) +#if __has_builtin(__alloc_size__) || (!defined (__clang__) && ((__GNUC__ > 4) || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3))) #define G_GNUC_ALLOC_SIZE(x) __attribute__((__alloc_size__(x))) #define G_GNUC_ALLOC_SIZE2(x,y) __attribute__((__alloc_size__(x,y))) #else -- 2.1.0 ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: help wanted for implementing GdkGLContext on Windows and MacOS X
On Thu, Nov 20, 2014 at 3:31 AM, Emmanuele Bassi wrote: > 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. > The officially supported way to build the GTK stack on OSX uses jhbuild, and this is also how Gnome applications like Gedit build their app bundles [1]. So building a stripped-down libepoxy shouldn't affect any other applications who would want to use libepoxy's X11 capabilities outside of the jhbuild environment. I guess it's another story for those wanting to build GTK via Homebrew, Macports, or other similar systems, though. On 19 November 2014 08:10, Jasper St. Pierre 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 > It did, thanks! > > 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 > > wrote: > >> > >> On Sun, Nov 16, 2014 at 6:32 AM, Emmanuele Bassi > 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. > [1] http://blogs.gnome.org/jessevdk/2014/09/02/gedit-3-14-for-os-x-preview/ -- Philip ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
