| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
We only use Meson, so we can drop a lot of unnecessary files.
|
|
|
|
|
|
|
|
|
| |
We depend on C99 functions in the math library; if the math library is
not found, or if it's not C99-compliant, we have fallbacks in place.
Commit 68da550e817b1269d1ccfdeeec2a53ddbd7b920a removed the checks, and
we ended up compiling the fallbacks even when the C library provided
these symbols — leading to a build error caught by Continuous.
|
|
|
|
|
|
| |
The uninstalled pkg-config file is generally considered pointless;
building multiple modules should not look into source directories of
the dependencies, but use a separate installation prefix.
|
| |
|
|
|
|
|
| |
Windows will not be using GIO to do mime-sniffing, but it's a
requirement on other platforms.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use AC_CHECK_LIBM to check for the math library. This
should also cover BeOS if necessary.
|
| |
|
|
|
|
|
|
| |
To calculate the rowstride without allocating memory!
https://bugzilla.gnome.org/show_bug.cgi?id=765094
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some supported compilers lack some C99 math functions that are beginning
to be used in the code, so this adds a fallback implementation for them,
namely round() and lrint(), where the fallbacks are used if they are not
found during configure.
For Visual Studio builds, config.h.win32.in is updated to reflect the
situation on various Visual Studio versions as Visual Studio builds
do not use autotools.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the autotools scripts so that we can support Visual Studio 2017 by
copying the 2010 projects and updating items as necessary.
Note that the toolset version format for 2017 has changed, so we now
allow a custom string to be set and thus be used; otherwise the toolset
version string is generated as it was before.
Also note that Visual Studio 2017 aims to be compatible with Visual Studio
2015 at the CRT level, meaning that one should be able to use 2017-compiled
binaries with 2015-compiled binaries without problems.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Return an error if the image width or height are too big to fit in the
BMP size fields.
This bumps our GLib dependency to 2.48.0, as it uses
g_uint_checked_mul(). If you want to backport this fix, it’s probably
best to use __builtin_umul_overflow() directly (if compiling using GCC
or another compiler which supports it).
Coverity ID: 1388532
https://bugzilla.gnome.org/show_bug.cgi?id=777315
|
|
|
|
|
|
| |
Now that scaling down by huge factors is fixed, we can deprecate the
work-arounds from other libraries. This means they require the newer
version, so bump the version so it's identifiable.
|
|
|
|
|
|
|
|
| |
This moves the Visual Studio project files and related items under win32/
so that people can go one less directory layer down to the Visual Studio
projects. This also makes things in sync with what is now on GLib and GTK+,
and cleans up the Visual Studio 201x projects as some items can actually be
combined.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
So that gnome-desktop can rely on a newer version of gdk-pixbuf with the
external thumbnailer.
|
|
|
|
|
|
|
|
|
|
|
| |
So that broken images, or images that use too much RAM can get killed
without prejudice.
_gdk_pixbuf_new_from_uri_at_scale() and
gnome_desktop_thumbnail_scale_down_pixbuf () are directly from
gnome-desktop.
https://bugzilla.gnome.org/show_bug.cgi?id=768062
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|