Tor Lillqvist wrote:
You must have updated your GTK+ installation only partially and use the etc/gtk-2.0/gdk-pixbuf.loaders file from a previous version of GTK+ with a new libgdk_pixbuf-2.0-0.dll. Or the other way around.
I don't know about the original poster but this is not the case for me. I just confirmed by wiping my stystem and starting over. I am using a newer bundle from http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.16/ and the problem is the same.
There is code in gdk_pixbuf that checks if the start of the path to a loader DLL in the gdk-pixbuf.loaders file matches the compiled-in "install" path (the c:/devel/target/<hexstring>) and then automatically replaces that with the actual installation path deduced from the DLL location at run-time.
With the above mentioned bundle, I find the gdk-pixbuf.loaders file has paths like this one (as did the original poster) "c:/devel/target/ef5505c4734684042571adef150ddfe8/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.dll" but libpixbufloader-png.dll doesn't exist anywhere on my system. May I then conclude that the gtkmm bundle is broken? Damon Register _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
