GNOME Bugzilla – Bug 793256
Add build options to disable specific extension initialisation
Last modified: 2018-05-24 20:11:32 UTC
In specific use cases, where disk space is limited, it could be nice if there was some build parameters to skip the extension initialisation (or the entire extension). The static initialization ensure that symbols are used, which means linker techniques that excludes unused symbols no longer work when the extension are effectively not used. This of course only apply to static linking. Another possible would to out compile that code, though this is much more intrusive. Let me know your opinion. For more details, watch Olivier's presentation: fosdem.org/2018/schedule/event/gstreamer_for_tiny_devices His hack patch could serve as a reference.
Created attachment 368076 [details] [review] Hack patch So it doesn’t get lost, here’s Olivier’s hack patch. (Definitely not to be committed in its current form!)
As briefly discussed on IRC today, I’d be in favour of some approach to this, so that GLib is more amenable for use on Android/iOS. tpm says it should be possible to get GLib builds done on ci.gst.net for those platforms, which would go a long way to making me happy about the maintenance cost of supporting this kind of thing in GLib.
There's also https://bugzilla.gnome.org/show_bug.cgi?id=727798 and I should somewhere have a relatively huge patch disabling lots of GIO subsystems. I think it would be better to split GIO into meaningful parts though, e.g. GDBus, GMenu and all the desktop integration stuff does not really have anything to do with "IO". But that probably has to wait until GIO 3.0 :)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1334.