Is this the right place for reporting problems with gdk-pixbuf or does it have its own forum somewhere??
Basically… a few years ago I built the GTK+ support stack for Windows, using MSVC (which was a supported compiler back then). At the time, gdk-pixbuf was at version 2-36 although I only built the stack libs as 32-bit.
I’m now in the process of resurrecting everything and updating it all to 64-bit. Everything seems to have built successfully except for a strange runtime issue with gdk-pixbuf.
‘gdk-pixbuf-io.c’ contains a function called _gdk_pixbuf_get_module(). Its execution varies (depending on whether or not I #define GDK_PIXBUF_USE_GIO_MIME). For a 32-bit build it doesn’t seem to have much effect whether I #define it or not but things are very different for a 64-bit build…
Towards the end of _gdk_pixbuf_get_module() there’s a check to see if a variable called selected got set. For my 32-bit build it’s always correctly set by the time that test gets reached (i.e. it’s always non-NULL). But things are very different for a 64-bit build…
If I build with GDK_PIXBUF_USE_GIO_MIME #defined to 1, a 64-bit build will fail to read any image file of any type. And if GDK_PIXBUF_USE_GIO_MIME is undefined, some file types succeed (e.g JPG and BMP) whereas most fail (TIF / PNG etc).
Does this make sense to anyone here? For example does gdk-pixbuf need me to specify some extra #define(s) when building as 64-bit??
[Edit…] Or alternatively… do I need to #undef G_OS_WIN32 when building as 64-bit? I couldn’t find anything called G_OS_WIN64 so I’ve assumed I’ll still need G_OS_WIN32