Bastien Nocera wrote: > You can disable regex, SELinux and threads support, which should bring > down the size of glib. This is the size on my machine with regex > enabled, on a 64kB machine. > $ ll /lib64/libglib-2.0.so.0.1600.3 > 926k -rwxr-xr-x 1 root root 918k 2008-06-17 04:48 > /lib64/libglib-2.0.so.0.1600.3
Granted I don't have a slimmed-down glib installed, but on my desktop, glib is close to 5 times as big as libfprint. Way too big for a utility library. Unless disabling those features makes it more than 5 times smaller, it seems wasteful. I can't recall how big glib was when I compiled it for mipsel but it was way too big given the limited storage. > You mentioned wanting to make reader drivers selectable at compile > time. You could use GModule and make them all plugins, and include some > of them directly in the library binary, as GModule supports (using NULL > as the filename to g_module_open). GModule is pretty, but again I only class it as a minor increase in convenience. I think we can cleanly implement modularization without it. > It also hides a lot of stupid unix-y differences, runs on Windows, and > gives you a lot of useful convenience data types. You could also use > GSources to handle polling better in libfprint. The cross-platform stuff is nice, but (with embedded in mind) I don't really see us going much beyond the libc usage that we have already, all of which is available on windows. Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
