From: Dom Lachowicz (email@example.com)
Date: Mon Oct 27 2003 - 08:34:59 EST
> How tight is the glib dependency, any chance that
> the mini-glib in wv could be
> used, or that we could make a mini-glib for it that
> wouldn't be too big?
Quite tight. We'd need a real glib.
> I thought it depended on libxml2 as well (win32 abi
> uses expat).
It does use libxml2. Arguably, libxml2 is quite a bit
better, faster, and more robust than Expat and its DLL
is only about 160kb .
In reality, we're trading one set of dependencies for
another, while also ditching a bunch of UT_XXX code.
Gone: libole2, glib, expat, libiconv
New: libgsf, glib-2.0, libxml2
I don't think that a net gain of .5 or 1 MB is enough
to get fussy about. Especially since our most popular
plugins already require libgsf, and so their win32
installers include a copy of it, libxml2, and
glib-2.0. And we'd also be getting quite a bit more
flexibility and functionality in Abi's core out of
this on all of our platforms.
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
This archive was generated by hypermail 2.1.4 : Mon Oct 27 2003 - 08:36:17 EST