bmp headers contain separate fields for the number of colors,
and the bit depth. Catch the impossible n_colors > 1 << depth
and error early, before it causes a out-of-bounds memory
access when decoding the colormap.

https://bugzilla.gnome.org/show_bug.cgi?id=758991

Erroring out early if we find a bogus image depth is
the right thing to do, and avoids possible memory
overruns later on.

https://bugzilla.gnome.org/show_bug.cgi?id=747605

Benjamin Otte authored Oct 12, 2015 and Matthias Clasen committed Dec 14, 2015

In particular, add the canonical image/vnd.microsoft.icon

Move the math.h compatibility header from build/win32/math-compat to
build/win32/vs9, and copy it to build/win32/vs10 and build/win32/vs11
during 'make dist'.  This is because we don't need the header for
Visual Studio 2013 and later, and the math.h header shipped with
Visual Studio 2015 is now included in Windows 10 SDK's UCRT directory,
so the old way of including the compiler-shipped math.h by doing
'#include <../include/math.h>' would not work there.

This will fix the build on Visual Studio 2015.

https://bugzilla.gnome.org/show_bug.cgi?id=756381

Natanael Copa authored Oct 06, 2015 and Matthias Clasen committed Oct 06, 2015

The test case depends on GNU libc specific internals so we only run it
on GNU libc.

This fixes build on Linux with musl libc.

https://bugzilla.gnome.org/show_bug.cgi?id=756078

Handle also the situation where $(srcdir) == $(top_srcdir), so that this
can also be used in cases like librsvg and gobject-introspection.

Update the notes that this is also used for Visual Studio 2015 support,
and correct the MSVC_VER_LONG for MSVC 2015, which is 14, not 2015.

Also add a note that this can be used for other projects that have
Visual Studio build support.

The PCX, WBMP and RAS loaders have been dropped, so don't include them.
They should be dropped from gdk-pixbuf-io.c as well, otherwise if someone
is building with INCLUDE_xxx for them will get linker errors.

https://bugzilla.gnome.org/show_bug.cgi?id=721372