| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
png/jpeg are essential and have a fallback subproject so they are
enabled by default. tiff is not required by GTK and does not have a
subproject so it's set to 'auto' by default.
This fixes the case where tiff option was set to true by default but
meson setup was not aborting if the dependency was not found. Instead it
was failing at build time.
|
|
|
|
|
|
| |
This gives us an actual array, and lets Meson deal with the argument
parsing. It also gives us a default value that we can specify in the
meson_options.txt.
|
|
|
|
| |
Use 'default' as the default value, instead of 'none'.
|
|
|
|
|
| |
When building gdk-pixbuf as a sub-project, we want to yield the value of
the gtk_doc option to the super-project.
|
|
|
|
| |
We don't require gtk-doc.
|
|
|
|
| |
This is more consistent with other modules like GTK.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Libjasper is not really maintained any more, and has been dropped by
various Linux distributions over the years.
GdkPixbuf has not enabled the JPEG2000 loader by default in many years,
relying on downstream distributors to do so if they also shipped
libjasper. This means that it's unlikely anybody has relied on GdkPixbuf
to load a JPEG2000 image for the past 3 to 5 years, if at all.
The only other option for loading JPEG2000 images is to use OpenJPEG,
and for that there is an out of tree GdkPixbuf module available:
https://notabug.org/necklace/jp2-pixbuf-loader
Fixes: #152, #137
|
|
|
|
|
|
|
| |
And deprecate the `docs` one.
The `gtk_doc` option is shared across GNOME modules, so we should
conform to the established practice.
|
|
|
|
|
| |
Now that gdk-pixbuf-xlib has been moved out of tree into its own
repository, we can drop the `x11` build configuration option.
|
|
|
|
|
| |
Some linux-like platforms (e.g. Android) don't have a mime-info database
readily available for use.
|
|
|
|
|
|
| |
Like the Autotools build allows us to decide whether the tests should be
installed in a known location, we should have this option for the Meson
build.
|
|
|
|
|
|
| |
As per https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting
https://bugzilla.gnome.org/show_bug.cgi?id=790995
|
|
|
|
|
|
| |
As per https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting
https://bugzilla.gnome.org/show_bug.cgi?id=790995
|
|
|
|
|
|
|
|
|
|
| |
Don't make X11 support dependent on the presence of libX11 development
files on the build system.
Add an "x11" option to control whether X11 support should be built
or not.
https://bugzilla.gnome.org/show_bug.cgi?id=788672
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is currently a GDI+ image loader that is within the GDK-Pixbuf
codebase, which can serve as a basis for improvements to it or for
moving on to more modern Windows APIs/Frameworks such as Windows
Imaging Component (WIC).
Provide a Windows-only option to build it with Meson, which will mean
that when it is used the TIFF and JPEG loaders will not require libtiff
and libjpeg-turbo/IJG JPEG, but will use the GDI+ component of Windows
to deal with these images, along with BMP, GIF, ICO and images. This
will also enable the support of EMF and WMF images. For building this
set of loaders into the GDK-Pixbuf DLL, pass in 'windows' as a part of
the loaders passed into builtin_loaders, or pass in 'all' to
builtin_loaders in conjunction with this option.
This also means that by using this set of GDI+ loaders, we cannot use
any of the loaders (either in-house or those using the various
opensource libraries) for these formats, so these loaders will be
disabled as a result, since the MIME types, extensions and signature
of these formats are the same in the GDI+ loaders with their respective
counterparts that are otherwise built.
Note that PNG support still requires libpng, and JPEG2000 support still
requires libjasper, and in its current state, the TIFF and JPEG and ICO
(and hence ANI) support that are done by the opensource libraries and/or
the in-house loaders are still preferred over the GDI+-based ones since
in the current state they tend to work better, so this is provided as an
option.
https://bugzilla.gnome.org/show_bug.cgi?id=785767
|
|
|
|
|
|
|
|
|
|
| |
To ease packaging of the built binaries, provide an 'all' shorthand for
making all the buildable loaders built into the main GDK-Pixbuf library,
so that we do not need to distribute them as well, and makes it easier
so that one will not have to try to find and enter all the names of the
loaders that are shipped with GDK-Pixbuf.
https://bugzilla.gnome.org/show_bug.cgi?id=785767
|
|
|
|
|
|
|
|
|
| |
Add an option for relocatable builds, which is always enabled for
Windows builds as the GDK-Pixbuf DLLs can be moved about depending on
the packaging of the app. This is done as an option as relocatability
is supported on non-Windows platforms as well.
https://bugzilla.gnome.org/show_bug.cgi?id=785767
|
|
|
|
| |
Both API reference and man pages.
|
|
|
|
|
|
|
| |
Just like the Autotools build does.
We also provide a simple escape hatch for platforms where building
introspection data is too complicated at the moment.
|
|
Meson is a better build system than Autotools that has gotten traction
in the GNOME community.
The build is pretty much equivalent between Autotools and Meson, but at
this point it needs further testing to verify complete matching
behaviour.
The GDI-plus loaders are not currently built, as that will require
access to a platform I don't have in order to test them.
Additionally, the API reference is not being generated yet in Meson.
|