Like what is now done in GLib, ATK, GTK+ and some other libraries, make use
of compiler directives that is determined at configure stage (or
pre-configured) to export the symbols for the GdkPixbuf library.  This
cleans up things a bit, as the .symbols file will no longer need to
be maintained, as long as the GDK_PIXBUF_AVAILABLE_IN_* (or so)
annotation is marked in the header and the source file that defines
the function has config.h included first.

Clean up configure.ac and gdk-pixbuf/Makefile.am a bit as a result.

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

This is to make generating .pc files for the package easier for Visual
Studio builds.  Also make GlibEtcInstallRoot more consistent across the
board, and add setting entries for installation path to the Python
interpretor, also to make things easier for generating .pc files, as well
as building the introspection files.

And also: https://github.com/Alexpux/MINGW-packages/issues/987

From reading recent discussions, I believe static initiailizers
are handled OK now on all MSVC versions and MinGW-w64 GCC never
had any problems. So there is no need to avoid static libraries
globally (though avoiding them globally was never appropriate!)

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

As we're adding new APIs as well.

Instead of hardcoding enable_relocations for OS X, make this
a configure option.

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

This is another rarely seen, ancient image format, and nobody
is maintaining this loader inside gdk-pixbuf.

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

This is another very rarely seen, ancient image format,
and nobody is maintaining this laoder inside gdk-pxibuf.

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

This is a very rarely seen image format, and nobody is
maintaining this loader inside gdk-pixbuf.

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

This "adds" projects for Visual Studio 2015 builds by doing what we
did before: copy the Visual Studio 2010 projects and replace items in
there as necessary, as the formats of the project files for Visual
Studio 2010, 2012, 2013 and 2015 are largely the same.

David King authored Jan 27, 2015 and Matthias Clasen committed Jun 22, 2015

Use the PO_DEPENDS_ON_POT variable to (properly) ignore the timestamp of
the pot file, avoiding the need to touch the pot file in autogen.sh.

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

This reverts commit b7dff893.

build.gnome.org doesn't yet have a new-enough gettext for this.

David King authored Jan 27, 2015 and Matthias Clasen committed Mar 03, 2015

Use the PO_DEPENDS_ON_POT variable to (properly) ignore the timestamp of
the pot file, avoiding the need to touch the pot file in autogen.sh.

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

Kalev Lember authored Oct 28, 2014 and Bastien Nocera committed Nov 21, 2014

A few unneeded configure checks got carried over when gdk-pixbuf was
split out from gtk+. Drop them.

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

Andoni Morales authored Sep 28, 2014 and Bastien Nocera committed Oct 22, 2014

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

New API requires a version bump.

As the Visual Studio 2012/2013 are only slightly different from the Visual
Studio 2010 projects, we can provide support for them by using scripts to
copy the Visual Studio 2010 projects, and update the specific parts as
necessary.

Thus, there would be little maintenance overhead for these as only the 2010
projects need to be kept up-to-date as a result.  This might change when we
do get the stack working with WinRT/Metro, but that's going to be another
totally different issue.

Use --enable-coverage and make coverage to get it.