GNOME Bugzilla – Bug 580033
Don't use G_MODULE_BIND_LOCAL
Last modified: 2009-04-24 14:02:06 UTC
Using G_MODULE_BIND_LOCAL causes problems for introspecting plugins, since introspected symbols need to be globally available. And in any case, trying to use linker features to prevent symbol conflicts doesn't usually work out very well, it's better to just namespace properly.
Created attachment 133221 [details] [review] Don't use G_MODULE_BIND_LOCAL
There was some reason for using G_MODULE_BIND_LOCAL; I need to do bit of digging on this one.
OK, whatever the reason for this was, it's gone away and everything seems to work as expected without G_MODULE_BIND_LOCAL, so please just commit it.
See: http://bugzilla.openedhand.com/show_bug.cgi?id=1216 There was confusion when loading multiple plugins. Subsequent changes to MUTTER_PLUGIN_DECLARE() related to the switch to GTypeModule mean that it is no longer an issue, since the only symbols that are named the same in different modules are referenced with g_module_symbol().
Pushed to master on git.gnome.org. (Thanks for looking the patches over, Tomas)