summaryrefslogtreecommitdiff
path: root/gdk-pixbuf/meson.build
Commit message (Collapse)AuthorAgeFilesLines
* Include pixbuf loader API in the gir filePaolo Borelli2021-01-021-0/+1
|
* meson: Change introspection option to feature typeXavier Claessens2020-10-161-1/+3
| | | | This is more consistent with other modules like GTK.
* Remove the libjasper-based JPEG2000 loaderEmmanuele Bassi2020-06-261-1/+0
| | | | | | | | | | | | | | | | | 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
* gdk-pixbuf/meson.build: use darwin_versions in libraryTom Schoonjans2019-11-271-0/+1
|
* gif: Replace old LZW decoder with a stand-alone decoderRobert Ancell2019-07-291-1/+1
|
* build: Do not use `install` arg with configure_file()Emmanuele Bassi2019-06-291-1/+0
| | | | | | The `install` argument is implicitly set to true when specifying the `install_dir` argument. The argument is only used by Meson ≥ 0.50, and ever there, it's only ever useful if paired to a configuration option.
* build: Use idiomatic pkg-config generationEmmanuele Bassi2019-02-281-3/+1
| | | | | | We're still using the deprecated form of passing gdk-pixbuf as a library named argument, instead of the idiomatic positional argument, which lets Meson figure out all the needed dependencies.
* Merge branch 'issue-89' into 'master'Emmanuele Bassi2018-12-041-0/+4
|\ | | | | | | | | | | | | Add pkgconfig variables for binary utilities Closes #89 See merge request GNOME/gdk-pixbuf!12
| * Add variables for binary utilitiesEmmanuele Bassi2018-09-051-0/+4
| | | | | | | | | | | | | | It is useful for finding the correct path for the utilities, as it does not rely on PATH being set appropriately. Closes #89
* | build: add enum generation header to sources of built librariesMatthew Waters2018-10-171-0/+5
| | | | | | | | | | | | | | | | | | | | This ensures that the enums are generated before compiling the headers. Fixes variations on this error for different loaders pixbuf@@staticpixbufloader-qtif@sta/io-qtif.c.o' -c ../gdk-pixbuf/io-qtif.c In file included from ../gdk-pixbuf/io-qtif.c:34:0: ../gdk-pixbuf/gdk-pixbuf.h:40:46: fatal error: gdk-pixbuf/gdk-pixbuf-enum-types.h: No such file or directory
* | meson: Don't generate the loader cache when cross-compilingMatthew Waters2018-10-081-12/+17
| |
* | Workaround to install modules with .so suffix on osxIgnacio Casal Quinteiro2018-10-041-0/+7
| | | | | | | | | | | | | | The old autotools build system was create .so files instead of dylib and G_MODULE_SUFFIX does not take into account dylib suffixes so we should at least for now use .so until we have a better api to use than the one provided by gmodule.
* | build: Include gdk-pixdata.c when building GdkPixbuf-2.0.girIain Lane2018-09-121-1/+5
| | | | | | | | | | | | | | | | After the split, this wasn't included here. We need this file because it contains the annotations for gdk_pixbuf_new_from_inline - without those we generate broken introspection metadata. Closes #92
* | Ensure that building loaders.cache depends on modulesEmmanuele Bassi2018-09-051-0/+4
|/ | | | | | We're passing the full path to the shared modules, which confuses Meson. Closes #88
* Generate GdkPixdata introspectionissue-72Emmanuele Bassi2018-05-241-31/+62
| | | | | | | | | | | | | | | | | | | | | | 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
* meson: Generate the pkg-config fileEmmanuele Bassi2018-04-301-0/+18
| | | | | Instead of using a template, use Meson's pkgconfig module to generate the pkg-config file for us from the build targets.
* meson: Limit use of pixops static libraryEmmanuele Bassi2018-04-301-3/+6
| | | | | We really only care about it as a library in order to build a test. We can simply include the sources into the main shared library.
* meson: Install the marshalers headerEmmanuele Bassi2018-04-251-1/+3
| | | | | | | The generated marshalers are public API, and the header needs to be installed, even though nobody should be using them. https://bugzilla.gnome.org/show_bug.cgi?id=795213
* build: Update the introspection rulesEmmanuele Bassi2018-02-121-15/+17
| | | | | | | | | | We should not be using cross-compilation to gate the generation of introspection data; it's perfectly possible to use a helper binary to run g-ir-scanner when cross-compiling — in fact, that's what projects like Yocto already do. We should also return a target for the introspection data, to allow using gdk-pixbuf as a sub-project.
* build: Remove "with" from Meson build optionsBastien Nocera2017-12-051-1/+1
| | | | | | As per https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting https://bugzilla.gnome.org/show_bug.cgi?id=790995
* build: Remove "enable" from Meson build optionsBastien Nocera2017-12-051-6/+6
| | | | | | As per https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting https://bugzilla.gnome.org/show_bug.cgi?id=790995
* build: Fix invalid syntaxBastien Nocera2017-09-191-1/+1
| | | | WARNING: Passed invalid keyword argument "source" in gdk-pixbuf/meson.build line 243.
* build: Support Windows components-based loaderChun-wei Fan2017-09-071-3/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* build: Fix libjasper detection and usage on Meson/MSVCChun-wei Fan2017-09-071-3/+5
| | | | | | | | | | | | | In order for MSVC builds that utilize libjasper to work, we need to ensure that JAS_WIN_MSVC_BUILD is defined when we check for jasper/jasper.h, and that same macro is defined when we compile io-jasper.c on MSVC. We also need to look for libjasper.lib on MSVC in case that jasper.lib cannot be found, as the Visual Studio projects for libjasper produces libjasper.lib upon build. https://bugzilla.gnome.org/show_bug?id=785767
* build: Allow 'all' shorthand for builtin_loaders build optionChun-wei Fan2017-08-211-2/+2
| | | | | | | | | | 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
* build: Build the .rc file on WindowsChun-wei Fan2017-08-171-0/+12
| | | | | | | | Like the autotools and Visual Studio builds, include the .rc file in the main GDK-Pixbuf DLL so that people can determine its version info more easily. Determine current - age as we did in the autotools builds. https://bugzilla.gnome.org/show_bug.cgi?id=785767
* build: Fix Meson builds using builtin loadersChun-wei Fan2017-08-171-2/+3
| | | | | | | | | | | | | | | | | We need to ensure that the loaders that are to be built into the main GDK-Pixbuf library is built as follows: -The individual loader sources are built with the corresponding INCLUDE_xxx macro defined. -The GDK-Pixbuf library itself must be built with all of the INCLUDE_xxx macros defined for building the individual loaders that we are building into the main GDK-Pixbuf library There is also a typo for the macro to make the loaders built into the GDK-Pixbuf library, so correct that as well (-DINCLUDED_xxx -> -DINCLUDE_xxx). https://bugzilla.gnome.org/show_bug.cgi?id=785767
* meson: Use include_directories references throughoutJan Alexander Steffens (heftig)2017-08-131-3/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=785964
* meson: Support installed testsEmmanuele Bassi2017-08-021-1/+1
| | | | | We want to be able to run the gdk-pixbuf tests after installing them in a known system location, especially when running CI.
* meson: Install enum types header in the right placeEmmanuele Bassi2017-08-021-1/+2
|
* meson: Generate introspection dataEmmanuele Bassi2017-08-021-6/+30
| | | | | | | 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: Use the appropriate name for the shared libraryEmmanuele Bassi2017-08-021-1/+1
| | | | | The name is `gdk_pixbuf-2.0`, not `gdk-pixbuf-2.0`, I guess for historical reasons.
* meson: Add gdk-pixbuf-macros.h to the installed headersEmmanuele Bassi2017-08-021-3/+4
| | | | It was lost in the port.
* Initial implementation of a Meson buildEmmanuele Bassi2017-08-011-0/+178
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.
View Lorry Controller Status