Support for static building
Some vendors want to link the tinymail framework statically with their binaries. This is often used on mobile phones and other devices. Tinymail currently supports some of this because its build environment uses libtool. So it will automatically create a .a and .la already.
You can help adjusting the build environment to support both a normal compilation (with lots of shared libraries) and a static one. One that you can statically link with an application binary.
Howto
- Make camel-lite optionally static (or copy the source in libtinymail-camel/camel for example using svn:external)
- Integrate with static versions of Camel (camel-lite-builder) for libtinymail-camel
- Integrate with static versions of Gtk+ for libtinymailui-gtk
- Static version of glib, maybe?
