| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
from the gAMA PNG chunk but not if sRGB mode is already set.
|
|
|
|
|
|
| |
From http://www.libpng.org/pub/png/book/chapter10.html#png.ch10.div.6
An sRGB-aware decoder should ignore gAMA and cHRM whenever an sRGB
chunk is present.
|
|
|
|
|
| |
This tells people that building on Visual Studio is now done using Meson
and outlines the steps that are required for the build.
|
|
|
|
|
|
| |
It already takes about 20 seconds on my Core i7, and it can get worse
when running multiple tests in parallel, so it's a prime candidate for
timeouts on our CI infrastructure.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=775229
|
|
|
|
| |
We don't need them any more.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
tiff: fix include of windows.h on case-sensitive filesystems
See merge request GNOME/gdk-pixbuf!10
|
|/
|
|
|
| |
On case-sensitive filesystems, such as when cross-compiling from Linux,
including Windows.h will result in an error.
|
|
|
|
|
| |
We generate a random builddir, so we need to modify the `paths` key for
the artifacts we store on CI failure.
|
|
|
|
| |
We're not using Bugzilla any more.
|
|\
| |
| |
| |
| | |
Few fixes for Visual Studio builds
See merge request GNOME/gdk-pixbuf!8
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Visual Studio builds do not assume the presence of a shell script
interpreter but would normally use cmd.exe, which would make the post
install shell script useless in such situations.
Fix this by adding a Windows .bat port of the post install script, to be
used on Visual Studio builds, which may be usable on MinGW builds if
MinGW builds can be done directly in cmd.exe.
|
|/
|
|
|
| |
Fix the checks as set10() will still set the macros to 0, which will
break the build when we compile conditionally using #if[n]def.
|
|\
| |
| |
| |
| | |
Run the test suite on the CI pipeline
See merge request GNOME/gdk-pixbuf!7
|
| |
| |
| |
| |
| |
| |
| |
| | |
Meson allows us to classify each test in the test suite using one or
more tags; this allows us to specify what kind of tests we want to run
inside our CI infrastructure, for instance by tagging the "slow" tests
that should have a special time out value, or that should only be run on
demand to avoid hammering the build server.
|
| |
| |
| |
| |
| |
| |
| | |
The gdk-pixbuf test suite can be pretty intense, so we're going to need
to check if we can get it to run.
First things first: enable it.
|
|\ \
| | |
| | |
| | |
| | | |
Fix the macOS build
See merge request GNOME/gdk-pixbuf!5
|
| | |
| | |
| | |
| | | |
Instead of just for gdk-pixbuf-xlib.
|
| | |
| | |
| | |
| | | |
We're missing OS_LINUX and OS_DARWIN pre-processor symbols.
|
|/ /
| |
| |
| | |
We're not testing for bind_textdomain_codeset() and setrlimit().
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
jasper: Avoid a deprecation warning
Closes #73
See merge request GNOME/gdk-pixbuf!4
|
| | |
| | |
| | |
| | | |
Move the build options into the YAML file while we're at it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The jas_stream_memopen() function uses any non-negative buffer size with
a NULL buffer to signify that the buffer will be allocated internally
and set to grow as needed. In the future, jas_stream_memopen() will be
replaced by a function that takes a size_t instead of a signed integer.
Passing -1 as the buffer size trips a run time deprecation warning, so
we can just use 0 and keep compatibility between the old libjasper and
newer versions.
Closes: #73
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Generate GdkPixdata introspection
Closes #72
See merge request GNOME/gdk-pixbuf!2
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The GdkPixdata API is built as part of the GdkPixbuf shared library,
but:
- it has its own namespace
- it has its own header file
- it's mostly meant for C applications
- it is deprecated
Consumers of the introspection data cannot access this API by using the
GdkPixbuf-2.0 GIR, as the namespace and included headers are different.
Instead of kludging the API, let's move the GdkPixdata introspection
out of the GdkPixbuf-2.0 GIR and into its own module.
This is an introspection ABI break, but there aren't many consumers of
GdkPixdata out there, and it's preferable to straight including the
gdk-pixdata.h header into gdk-pixbuf.h.
Fixes #72
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Deprecate GDK_INTERP_HYPER
Closes #3
See merge request GNOME/gdk-pixbuf!3
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The hyperbolic filter has been broken for the past 12 years, and nobody
is going to fix it, now, as pixel operations in GdkPixbuf have been
thoroughly superseded by Cairo.
The only user of GDK_INTER_HYPER in tree is the thumbnailer code, which
cannot use Cairo for dependency reasons.
Closes: #3
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make the X11 dependency less automagic
Closes #77
See merge request GNOME/gdk-pixbuf!1
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the x11 option is enabled then we require X11.
We should use a `dependency()` object in order to check for Xlib,
instead of checking for libX11 being available.
Closes #77
|
| |/ /
|/| |
| | |
| | |
| | | |
We're going to land deprecations, and we dropped Autotools, so this is a
good moment to bump up the version.
|
| | |
| | |
| | |
| | | |
The markdown of the Contribution guide has a broken link anchor.
|
| | |
| | |
| | |
| | | |
The aggregate license is LGPL v2.1+.
|
| | |
| | |
| | |
| | |
| | | |
Since we are still in a stable release series, ensure that the code
still builds on pre-C99 compilers.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The vast majority of GdkPixbuf is released under the terms of the GNU
Lesser General Public License, version 2.1 or later.
The following files are released under the terms of the GNU Library
General Public License, version 2 or later:
```
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlib.c
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlib-drawable.c
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlib.h
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlib-private.h
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlib-render.c
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlibrgb.c
contrib/gdk-pixbuf-xlib/gdk-pixbuf-xlibrgb.h
gdk-pixbuf/io-pnm.c
gdk-pixbuf/io-tga.c
gdk-pixbuf/io-xbm.c
gdk-pixbuf/make-inline-pixbuf.c
gdk-pixbuf/queryloaders.c
```
The aggregate license of the GdkPixbuf project is the Lesser GPL v2.1 or
later.
Closes: #67
|
|/
|
|
|
| |
Makes it easier to see what was enabled, what's going to be built, and
where it's going to be installed.
|
|
|
|
|
| |
Build inside a temporary directory, and ensure that the local
run-docker.sh script imports the repo inside the Docker container.
|
|
|
|
|
| |
The man page for gdk-pixbuf-csource is generated via xsltproc, so
there's no need to keep the troff version in tree.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Existing GdkPixbuf API like gdk_pixbuf_new_from_file_at_size and
gdk_pixbuf_get_file_info have grown smarter since this code was
written. They are now better at selecting the best GdkPixbufLoader for
a given file.
As a side-effect, this also prevents leaking the GFile and its URI,
but those are minor issues since the thumbnailer has a very short life
span
https://bugzilla.gnome.org/show_bug.cgi?id=778517
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, it's not possible to get the dimensions of the original
image from a scaled GdkPixbuf. This is problematic for thumbnailers
because they want to embed the original dimensions into the resulting
thumbnail file. The only way to get this information is to either
decode the full-resolution image and then downscale it, even when the
decoder supports downscaling on-the-fly; or to re-implement large
chunks of code to avoid decoding the full-resolution image and
retain the original dimensions.
Exposing the original dimensions as options simplifies the thumbnailer
without affecting performance.
https://bugzilla.gnome.org/show_bug.cgi?id=778517
|
|
|
|
|
|
|
|
|
|
| |
All the options are stored under the "gdk_pixbuf_options" key, and only
those were being copied after applying the orientation. Anything else
stored under any other key gets lost with the unoriented GdkPixbuf.
Fallout from 06cf4c78067203b78acbfb29862350cdb8200b73
https://bugzilla.gnome.org/show_bug.cgi?id=778517
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=795705
|
|
|
|
| |
Otherwise the commit hook on git.gnome.org will complain.
|
|
|
|
|
|
|
|
| |
We haven't built them on anything that isn't a 32bit IA platform, and
we could probably get better mileage out of the currently implemented
pixops just by rearranging the C code and letting compilers do the
optimizations for us. We should definitely consider either using pixman
directly, or replacing slow pixops with SSE builtins, instead.
|
|
|
|
|
|
| |
The `docs` directory is empty, and gdk-pixbuf is not part of GTK any
more, so there's no point to have the API reference under a separate
directory.
|
|
|
|
|
|
| |
We use Meson, now. The Meson build has been tested for almost a year in
our continuous integration pipeline, and it's functionally equivalent to
the Autotools one.
|
|
|
|
|
| |
Once we migrate GdkPixbuf over to GitLab, we should already have all the
required bits in place for running a continuous integration pipeline.
|