| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| | |
build: Clean up search for deps on Visual Studio
See merge request GNOME/gdk-pixbuf!131
|
| |
| |
| |
| |
| | |
Like the previous commits, use CMake's builtin support to look for
libtiff, which will clean things up a bit in the build files
|
| |
| |
| |
| |
| |
| |
| | |
Like wat we did for libpng, do likewise to look for libjpeg (or
libjpeg-turbo) via CMake's builtin support, so that we can clean up the
build files and have CMake do a more comprehensive manual search for
libjpeg or libjpeg-turbo.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We can use CMake's built-in search for the libpng headers and libraries
for Visual Studio-like compilers; however, we must use 'png' instead of
'libpng' for the package name for this to work.
This will cover the manual headers and .lib search in a more
comprehensive way, which CMake will handle for us and it is an
optionally-installed item for Visual Studio 2017 and later, and is very
commonly used on Windows dev environments.
Also use a common variable to indicate whether we are using an MSVC-like
compiler, to save future typing.
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
Use the latest from `meson wrap`.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
- When png/jpeg/tiff option is set to true it should abort when
dependency cannot be found one way or another.
- Use libjpeg-turbo meson port instead of libjpeg from wrapdb to fix
build on Windows.
- Rely on libpng.pc instead of checking each individual version.
Fixes: #182
|
|
|
|
|
|
|
|
|
| |
Follow the same pattern as the libpng checks:
1. look for libjpeg via pkg-config
2. if pkg-config fails, and we're using the MSVC toolchain, look
for header and library
3. if that fails, fall back to the libjpeg subproject
|
|
|
|
|
|
|
|
|
| |
meson can't do function checks for subprojects, since
these have not been built yet at configure time. So,
check if we are in that case and bypass the checks.
The libjpeg we build as a subproject is new enough
to have those functions, anyway.
|
|
|
|
|
|
|
| |
With meson 0.56, this can be done more elegantly with
allow_fallback and a [provide] section in the wrap
files, but with 0.55, we need to explictly mention
the variable names in the meson file.
|
|
|
|
|
|
| |
We are checking for libjpeg only if we find a header to include, but the
dependency check with pkg-config, and the fallback with a wrap file,
should happen outside of that check.
|
| |
|
| |
|
|
|
|
| |
The version of Meson shipped with Fedora 33.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Avoid the whole shell/batch file shenanigans.
|
|
|
|
|
|
|
|
|
|
| |
GdkPixbuf without PNG and JPEG loaders is less than useful for loading
assets in GTK (and anywhere else, really).
We go to great lengths to ensure that both the PNG and JPEG loaders are
built by default, to the point of including subprojects for libpng and
libjpeg. Let's avoid any doubt, and ensure that those loaders are also
included in the default shared library.
|
|
|
|
| |
Just like we documented it.
|
|
|
|
|
| |
Drop deprecated functionality, and use the appropriate functions and
objects to check for variables and generate the summary.
|
|
|
|
| |
Avoid hard-coding the dependency object into the meson.build file.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Fix build for Android
See merge request GNOME/gdk-pixbuf!104
|
| |
| |
| |
| | |
Similarly to what we do on Windows and macOS.
|
| | |
|
| | |
|
| |
| |
| |
| | |
We want to ship the generated API reference in the release archive.
|
|/
|
|
|
| |
The argument for additional dependencies is `dependencies`, not
`dependency`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Link with -lintl if needed to avoid the following build failure with
some toolchains (e.g. uclibc or musl):
/home/giuliobenetti/autobuild/run/instance-0/output-1/host/opt/ext-toolchain/bin/../lib/gcc/mips64el-buildroot-linux-uclibc/5.5.0/../../../../mips64el-buildroot-linux-uclibc/bin/ld: gdk-pixbuf/libgdk_pixbuf-2.0.so.0.4200.2.p/gdk-pixbuf-util.c.o: in function `_gdk_pixbuf_init_gettext':
gdk-pixbuf-util.c:(.text+0xbc0): undefined reference to `libintl_bindtextdomain'
/home/giuliobenetti/autobuild/run/instance-0/output-1/host/opt/ext-toolchain/bin/../lib/gcc/mips64el-buildroot-linux-uclibc/5.5.0/../../../../mips64el-buildroot-linux-uclibc/bin/ld: gdk-pixbuf-util.c:(.text+0xbc8): undefined reference to `libintl_bindtextdomain'
Fixes:
- http://autobuild.buildroot.org/results/894359558100ea9637feba16deaf99923805d0f2
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
|
|
|
|
|
|
| |
Since the gen-resources.py needs to call glib-compile-resources, we need
to figure out where the binary is, and tell gen-resources.py to use
that, instead of relying on it being in the PATH.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's still a free-form field, but we should at least adhere to a machine
parseable standard.
|
|
|
|
| |
The 0.48.1 base version is positively *ancient*.
|
| |
|
| |
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On FreeBSD, macros such as _POSIX_C_SOURCE and _XOPEN_SOURCE are used as
a means to disable features instead of enabling features. Therefore,
setting a macro to a value which is too small can make required features
become unavailable.
Commit f57bec3322921631c322b7d151fb129125b9d80d sets _XOPEN_SOURCE to
500 and causes compilation errors on FreeBSD because of missing C99
support. FreeBSD libc automatically sets _POSIX_C_SOURCE to 199506 when
_XOPEN_SOURCE is set to 500. Since 1995 < 1999, this also means all C99
functions are disabled. To fix it, use a value matching the current
definition of _POSIX_C_SOURCE=200809, which is _XOPEN_SOURCE=700.
|
|
|
|
| |
Fixes: #128
|
|
|
|
|
|
| |
This avoids the build from erroring out due to warning/error C4819 (Unicode
handling issue in the compiler), which is likely to occur on Chinese, Japanese
and Korean locales
|