GNOME Bugzilla – Bug 612918
Support disabling X11 extensions
Last modified: 2011-01-07 01:35:36 UTC
Hi, The attached patch from Cyril Brulebois <kibi@debian.org> makes it possible to disable X11 extensions support even when they are installed. We want this in Debian as we build GTK+ with extensions enabled for the normal build, but disable them for the special build that will be used in the graphical installer (so the extensions are installed and it was not posible to disable it).
Created attachment 156161 [details] [review] Support disabling X11 extensions
Why do you need that ? If there are bugs in gdk with dealing with the absence of extensions in the server, we need to fix those.
It's not because there are bugs, but because the graphical installer needs to be as small as possible, so we disable everything that is not strictly necessary (in gtk+ and everywhere)
(and this means we don't need to ship many X libs)
It'd be great if this could be applied, at least to GTK+3.
Created attachment 177521 [details] [review] Support disabling X11 extensions Here's an updated patch for git master. We already support this for other extensions. And these ones aren't mandatory, i.e. it's already possible to build gtk+ without them, so I see no harm in applying this. Can I push this to master?
Somewhat reluctantly. I hate to have more options to look after... Can we arrange things so that the default is "maybe" and we fail the build if there is an explicit --enable, but the extension is missing ? With that, I'll accept it for gtk3
Created attachment 177536 [details] [review] Support disabling X11 extensions Makes sense to me. Updated to do that. Removing e.g. xfixes.pc and doing a ./configure --enable-xfixes results in: configure: error: XFixes support requested but xfixes not found
Ok, looks good to me now. But I've done some configure.ac revamp recently, so you'll have to rebase the patch before committing it. Note that we now maintain a list of extensions in the X_EXTENSIONS (for summary display purposes)
Thanks. I've updated it to apply again and pushed to master as ec15c405cf6354e9267e7e6b7ce878c519bffe4c