Re: MS Windows packages and modularity

["Tor Lillqvist" <tml iki fi>]

> > Was there a compelling reason for this reversion?

Not really. As has already been said, if/when the GDI+ -based pixbuf
loaders would be used, then it would hopefully be 100% clear that it
makes sense to build them as built-in in the gdk-pixbuf DLL. But now
when I was forced to revert to the libgpej and libtiff -based loaders,
there are two more or less equivalent choices, both which have their
disadvatages: either 1) build separate png, jpeg and tiff loaders,
which means there are more files to distribute for people who want to
minimize the number of files in the GTK+ runtime and still be able to
load jpef or tiff files, or 2) build built-in loaders which means the
png, jpeg and tiff DLLs are required even for a GTK+ runtime used in a
situation where it doesn't use any png, jpeg and tiff files.

Would the best solution be to build the png, jpeg and tiff libraries
as static libraries, and link them statically into gdk-pixbuf?

--tml