summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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
* Emit a summary of the configurationEmmanuele Bassi2018-05-241-0/+21
| | | | | Makes it easier to see what was enabled, what's going to be built, and where it's going to be installed.
* ci: Update the scriptsEmmanuele Bassi2018-05-232-5/+12
| | | | | Build inside a temporary directory, and ensure that the local run-docker.sh script imports the repo inside the Docker container.
* Remove gdk-pixbuf-csource man pageEmmanuele Bassi2018-05-151-91/+0
| | | | | The man page for gdk-pixbuf-csource is generated via xsltproc, so there's no need to keep the troff version in tree.
* thumbnailer: Simplify the code by reusing existing GdkPixbuf APIDebarshi Ray2018-05-011-201/+8
| | | | | | | | | | | | | 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
* loader: Expose the dimensions of the original imageDebarshi Ray2018-05-011-1/+25
| | | | | | | | | | | | | | | | 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
* thumbnailer: Don't lose the dimensions of the original imageDebarshi Ray2018-05-011-5/+5
| | | | | | | | | | 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
* Change to more compatible shell locationBrendan L2018-05-011-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=795705
* Add description field to the DOAP fileEmmanuele Bassi2018-04-301-0/+1
| | | | Otherwise the commit hook on git.gnome.org will complain.
* Drop the MMX assembly optimizationsEmmanuele Bassi2018-04-308-1014/+3
| | | | | | | | 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.
* Move the API reference down two levelsEmmanuele Bassi2018-04-3016-4/+2
| | | | | | 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.
* Drop Autotools buildEmmanuele Bassi2018-04-3070-8210/+0
| | | | | | 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.
* Prepare for GitLab CIEmmanuele Bassi2018-04-304-0/+86
| | | | | Once we migrate GdkPixbuf over to GitLab, we should already have all the required bits in place for running a continuous integration pipeline.
* docs: Add a contribution guideEmmanuele Bassi2018-04-301-0/+141
| | | | Outline a contribution workflow, and how GdkPixbuf is logically split.
* docs: Fill out the README fileEmmanuele Bassi2018-04-302-0/+70
| | | | | It's desolate, at the moment, and free software projects without a decent README are a bit sad.
* docs: Hide Xlib typesEmmanuele Bassi2018-04-301-0/+9
| | | | We cannot expand those, as Xlib does not come with a gtk-doc index.
* docs: Add missing symbols indexesEmmanuele Bassi2018-04-301-0/+16
|
* docs: Remove an outdated exampleEmmanuele Bassi2018-04-301-40/+3
| | | | | | | The "handling an expose event" example is badly outdated, referencing concepts and practices that were deprecated halfway through the GTK 2.x development. These days, it's going to confuse people more than help them.
* docs: Add unused symbols to the API referenceEmmanuele Bassi2018-04-301-0/+11
|
* meson: Generate the pkg-config fileEmmanuele Bassi2018-04-303-33/+28
| | | | | 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-302-9/+17
| | | | | 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: Use convenience functions for compiler checksEmmanuele Bassi2018-04-301-11/+7
| | | | | | | Avoid a bunch of array iterations. The get_supported_link_arguments() call is gated on a Meson version check, to avoid requiring a bleeding edge stable version.
* meson: Bump up the required version of MesonEmmanuele Bassi2018-04-301-1/+1
| | | | Use a less ancient baseline.
* Update the DOAP fileEmmanuele Bassi2018-04-301-3/+11
| | | | Add myself as a maintainer.
* docs: Update list of ignored headersEmmanuele Bassi2018-04-301-1/+9
| | | | Like we did for Meson, do this for the Autotools build.
* Update Romanian translationDaniel Șerbănescu2018-04-301-407/+632
|
* meson: Add post-install scriptEmmanuele Bassi2018-04-292-0/+24
| | | | | | | If we're installing gdk-pixbuf ourselves, we should generate the loaders cache file — unless DESTDIR is set or we're cross-compiling, in which case we assume that there's a packaging system hook in place to do this at the end of a full build.
* meson: Add option for installing testsEmmanuele Bassi2018-04-292-4/+10
| | | | | | 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.
* docs: Update links to GDKEmmanuele Bassi2018-04-293-8/+7
| | | | | Remove long since gone intra-library links, and point to the API reference website instead.
* docs: Remove a dead linkEmmanuele Bassi2018-04-291-1/+1
|
* Silence two compiler warningsEmmanuele Bassi2018-04-291-3/+2
| | | | | | | | | | | We have two "set but unused variable" warnings coming from gdk-pixbuf-xlib. The first is caused by an unnecessary variable used to hold the return value of XGetWindowAttributes(); we don't do anything with it, and it's way too late for changing the behaviour of the function to bail out on error. The second is caused by a variable that is only used when a debugging printf() is compiled in; to avoid the warning without creating even more complex macro hell, we tell the compiler that the variable is unused.
* Avoid a compiler warningEmmanuele Bassi2018-04-291-13/+7
| | | | | | | | If there are no built-in modules, the `builtin_module` variable is not used, and the compiler will warn about it. Since we're already using the variable inside a macro, we can just declare it inside the macro block and save us the trouble altogether.
* Fix permissions for C89 fallbacksEmmanuele Bassi2018-04-291-0/+0
| | | | A text file should not have the executable bit set.
* meson: Re-instate mediaLib supportEmmanuele Bassi2018-04-291-1/+15
| | | | | We dropped it with the Meson build port, and I'm not entirely sure it's still tested, but it doesn't cost us anything to re-enable the check.
* gdk-pixbuf-xlib: Fix out-of-bounds error in dithering loopBert Pauline2018-04-291-7/+12
| | | | | | | | | | | | | Use two loops to traverse the array of arrays `DM`, i.e. use `DM[y][x]` instead of `DM[0][i]`. This resolves a warning about undefined behavior when compiling with GCC with aggressive loop optimizations enabled. While we are at it: Move the variable definitions into the body of the outer if-statement. https://bugzilla.gnome.org/show_bug.cgi?id=748211
* meson: Install bug753605-atsize.jpgEmmanuele Bassi2018-04-251-0/+1
| | | | | Same as commit fc2d02ed908c524cc2831e5404d5f06b02e3f9fd, but for the Meson build.
* 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
* meson: Fix building the API referenceEmmanuele Bassi2018-04-251-7/+14
| | | | | We need to re-generate the gdk-pixbuf.types in order to include all public types; this requires fixing the list of ignored headers.
* meson: Fix no-X11 documentation buildQuentin Glidic2018-04-251-0/+1
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=794872 Signed-off-by: Quentin Glidic <sardemff7+git@sardemff7.net>
* tests: distribute test file for bug 753605 testJeremy Bicha2018-04-251-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=795210
* Fix introspection data for gdk_pixbuf_new, gdk_pixbuf_copy and ↵Iñaki García Etxebarria2018-04-252-3/+3
| | | | | | gdk_pixbuf_composite_color_simple https://bugzilla.gnome.org/show_bug.cgi?id=789935
* Plug a memory leak when using GBytesVitaly Kirsanov2018-04-251-0/+2
| | | | | | | Calling g_bytes_unref_to_data() will copy the contents of the bytes buffer, so we need to free the data. https://bugzilla.gnome.org/show_bug.cgi?id=787626
* meson: Install tests and test dataEmmanuele Bassi2018-04-251-61/+71
| | | | | | | | We're currently installing the test launchers and parts of the test data, but we're not installing the binaries and the whole suite of image data we have. https://bugzilla.gnome.org/show_bug.cgi?id=795527
* windows: rework loaders cache relocation supportChristoph Reiter2018-04-242-40/+82
| | | | | | | | | | | | | | | | | | | | | | | | Relocation works by recognizing paths in the loaders cache which start with the built time prefix and extract the relative path from that. This leads to the following problem when updating the cache: In case the package is build on another machine one has to either match the build directory layout or adjust the cache by hand for the resulting cache to stay relocatable. This commonly occurs with msys2 where mostly pre-build packages are used which are built on another machine and the cache gets generated at install time. Another case is updating the cache in a separate deployment environment. This patch takes the package installation directory as a base and writes relative paths into the cache when relocation is enabled. When loading the cache a relative path is made absolute by prepending the package base again. https://bugzilla.gnome.org/show_bug.cgi?id=776081
* 2.36.122.36.12gdk-pixbuf-2-36Matthias Clasen2018-04-073-2/+11
|
* Update Croatian translationgogo2018-03-171-2/+2
|
* Update Croatian translationgogo2018-03-171-149/+149
|
* Update Croatian translationgogo2018-03-171-458/+540
|
* Update Chinese (Taiwan) translationChao-Hsiung Liao2018-03-101-133/+133
|
* Update Turkish translationÇağatay Yiğit Şahin2018-03-081-151/+204
|
View Lorry Controller Status