Re: [Discuss] Make a thinner Glib/GTK+ to fit tiny device better
- Date: Thu, 15 Oct 2015 22:14:36 +0800
- From: cee1 <fykcee1@xxxxxxxxx>
- Subject: Re: [Discuss] Make a thinner Glib/GTK+ to fit tiny device better
2015-10-14 23:40 GMT+08:00 Nicolas Dufresne <nicolas.dufresne@xxxxxxxxxxxxx>:
> Le lundi 12 octobre 2015 à 23:24 +0800, cee1 a écrit :
> GLib is already broken up into a whide amount of shared library. Even
> though, shared library tend to create a small size overhead.
> Considering this is a supporting library, it's probably not ideal to
> try and disable random features. What we endup doing here, is using
> static build, so whatever you don't use can later be stripped. It's
> more work in regard to the LGPL.
Then, I'm imaging a procedure of "static building" subset of glib
symbols into a library, and clients link to it...
>> providing APIs to make GTK+(also GIO) easily integrated to other
>> loop, then we use epoll() on Linux, kqueue() onBSD or even
>> libdispatch - client code can use simpler event loop(e.g. no
>> no recursive main loop support)
> This is all fully supported.
For GStreamer, yes. But not for GIO or GTK+? I guess.
gtk-devel-list mailing list