GNOME Bugzilla – Bug 743917
Gtk modules must be compatible with both gtk 2 and 3
Last modified: 2015-02-04 12:52:48 UTC
Gtk prints a message on every start of applications when it cannot find a module. Thus, the only sane way to create a module that only works on gtk 2 or 3 is to create a no-op module for the other one. Fix that by introducing GTK3_MODULES and GTK2_MODULES which are read in addition to GTK_MODULES. I'm aware that we eventually want to move away from supporting modules at all. However, this would help us transitioning away from one of our modules for gtk 3, but keep it for 2 for the time being.
Created attachment 296004 [details] [review] Add support for loading gtk3-only modules Introduce GTK3_MODULES environment variable for modules that don't work in gtk3. The list of modules is now $GTK3_MODULES:$GTK_MODULES.
Created attachment 296005 [details] [review] Add support for loading gtk2-only modules Same in green for gtk 2.
I can see how GTK2_MODULES can make sense for transitioning away, but why add GTK3_MODULES ?
(In reply to comment #3) > I can see how GTK2_MODULES can make sense for transitioning away, but why add > GTK3_MODULES ? I agree and was unsure whether I should include the patch at all, but did so for symmetry. Are you okay with the gtk2 one?
Actually, I think I agree with the symmetry argument.
Comment on attachment 296005 [details] [review] Add support for loading gtk2-only modules Attachment 296005 [details] pushed as 436fe38 - Add support for loading gtk2-only modules
Attachment 296004 [details] pushed as 3e81653 - Add support for loading gtk3-only modules