From: Andy Stewart <email@example.com>
John Lato <firstname.lastname@example.org> writes:
> I just managed to install gtkglext with the quartz backend provided by gtk-osx.? This was much more
> work than it should be,
> although a lot of that is probably related to the packaging of gtkglext.
> If anyone's interested, instructions are at
I have seen you patches, to be honest, i don't like them.
Such as :
-foreign import ccall unsafe "gdk_x11_drawable_get_xid"
- gdk_x11_drawable_get_xid :: (Ptr Drawable) -> IO CInt
foreign import ccall unsafe "gdk_win32_drawable_get_handle"
gdk_win32_drawable_get_handle :: (Ptr Drawable) -> IO (Ptr a)
@@ -609,7 +607,7 @@
liftM toNativeWindowId $
(\(Drawable drawable) ->
- withForeignPtr drawable gdk_x11_drawable_get_xid
+ withForeignPtr drawable (error "drawableGetID not defined on OS X")
withForeignPtr drawable gdk_win32_drawable_get_handle
You just simple remove "gdk_x11_drawable_get_xid" for quartz backend,
but X11 backend, this function is exist.
IMO, If haven't any flag for quartz backend,
we should add below flag in gtk.cabal
Description: Flag for quartz backend, thereby disabling certain features.
then we can use "USE_QUARTZ_BACKEND" flag to disable
"gdk_x11_drawable_get_xid" on quartz backend.
Then you need pass "use-quartz-backend" to cabal explicitly when you install
gtk on quartz backend.
Other patches about quartz backend should use same way.