GNOME Bugzilla – Bug 738616
build-sys: Don't set GConf flags when it's disabled
Last modified: 2017-11-16 13:54:50 UTC
We currently always call PKG_CHECK_MODULES(GCONF, gconf-2.0) even when configure was called with --disable-gconf. If GConf development packages were installed, this will cause GCONF_CFLAGS/GCONF_LIBS to be set even though it's disabled, and the resulting gnome-session binary will end up linking with gconf. This patch reworks a little bit the GConf detection code so that it only calls PKG_CHECK_MODULES when GConf is enabled or auto-detected.
Created attachment 288658 [details] [review] build-sys: Don't set GConf flags when it's disabled
Created attachment 288661 [details] [review] build-sys: Remove unused GConf preprocessor #defines
Created attachment 288662 [details] [review] build-sys: Remove unused GTKBUILDER_DIR #define
We should just delete the gconf support; surely nobody wants that anymore?
Unless it's used for backward compatibility/migration purpose when moving from gnome 2 to gnome 3, this shoud probably be dropped indeed. Even if it's there for such purpose, it probably has been enough time that this could be dropped anyway.
Review of attachment 288658 [details] [review]: Added a patch in bug 787806 to remove it altogether.
Review of attachment 288661 [details] [review]: Ditto.
Review of attachment 288662 [details] [review]: And merged this in the meson porting patch in bug 787806.
All 3 patches should be taken care of in bug 787806, so closing this. Thanks for the pointers!