summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | queryloaders: add missing include for OSX when using relocationsIgnacio Casal Quinteiro2018-10-041-1/+5
|/ /
* | Update Chinese (Taiwan) translationYi-Jyun Pan2018-10-031-184/+187
| |
* | Update Serbian translationМарко Костић2018-09-291-185/+188
| |
* | Updated Danish translationAsk Hjorth Larsen2018-09-241-185/+187
| |
* | Added Slovenian translationMatej Urbančič2018-09-171-186/+189
| |
* | Update French translationCharles Monzat2018-09-161-187/+192
| |
* | Update Romanian translationDaniel Șerbănescu2018-09-161-187/+189
| |
* | Update Indonesian translationKukuh Syafaat2018-09-141-189/+192
| |
* | Update Latvian translationRūdolfs Mazurs2018-09-141-240/+189
| |
* | Update Hungarian translationBalázs Úr2018-09-131-239/+187
| |
* | Update Polish translationPiotr Drąg2018-09-131-188/+191
| |
* | Update Italian translationMilo Casagrande2018-09-131-188/+191
| |
* | Update Turkish translationEmin Tufan Çetin2018-09-131-241/+191
| |
* | Update Swedish translationAnders Jonsson2018-09-131-185/+188
| |
* | Updated Czech translationMarek Cernocky2018-09-131-235/+238
| |
* | Update German translationMario Blättermann2018-09-131-206/+199
| |
* | Update Brazilian Portuguese translationRafael Fontenelle2018-09-131-242/+192
| |
* | Merge branch 'wip/rishi/png' into 'master'Emmanuele Bassi2018-09-131-9/+28
|\ \ | | | | | | | | | | | | io-png: Fix various minor error handling bugs in the begin_load implementation See merge request GNOME/gdk-pixbuf!16
| * | io-png: Clarify and fix the error handlingDebarshi Ray2018-09-101-8/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Neither png_create_read_struct* nor png_create_info_struct can trigger a longjmp out of libpng. That's only documented as being possible with png_set_progressive_read_fn, even though, currently, it does not. The documentation [1] is being a bit simplistic when it says: "... you will need to update the jmpbuf field every time you enter a new routine that will call a png_*() function" On closer look, the documentation for png_create_read_struct* [2] and png_create_info_struct [3] clarify that they return NULL on error and don't longjmp. This is borne out by the libpng code, comments and examples. In light of this, the assumption that the error callback would set the GError when either png_create_read_struct* or png_create_info_struct fails is wrong. These functions can only fail if there was a request to allocate an absurdly large amount of memory that exceeds one of the limits encoded in libpng; or if the memory allocator returns NULL; or if there was a ABI mismatch caused by compiling and running against incompatible libpng versions. All those are either programming or integration errors or something extremely catastrophic - normally one wouldn't bother handling them as run-time failures. However, since the libpng documentation repeatedly mentions that the return value from these functions should be checked, it's wise to do so. The current location of the setjmp is confusing to the reader because one can be misled into thinking that there's no need to check the value returned by png_create_info_struct, or that a failure will lead to the error handler and a longjmp. It's better to move it closer to the fallible png_set_progressive_read_fn. Fallout from e8d0d8ed3d33ee6cedb75a394c36af3312b310ff [1] http://www.libpng.org/pub/png/libpng-1.2.5-manual.html#section-3 [2] http://refspecs.linuxbase.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Desktop-generic/libpng12.png.create.read.struct.1.html [3] http://refspecs.linuxbase.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Desktop-generic/libpng12.png.create.info.struct.1.html https://gitlab.gnome.org/GNOME/gdk-pixbuf/merge_requests/16
| * | io-png: Remove redundant NULL checkDebarshi Ray2018-09-101-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | png_destroy_read_struct is safe against both a NULL png_infop and pointer to a NULL png_infop. Fallout from e8d0d8ed3d33ee6cedb75a394c36af3312b310ff https://gitlab.gnome.org/GNOME/gdk-pixbuf/merge_requests/16
| * | io-png: Don't leak the png_infop in begin_loadDebarshi Ray2018-09-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | If lc->png_info_ptr is not NULL, then not passing it to png_destroy_read_struct will not release some resources. Fallout from e8d0d8ed3d33ee6cedb75a394c36af3312b310ff https://gitlab.gnome.org/GNOME/gdk-pixbuf/merge_requests/16
* | | Merge branch 'wip/gir-include-pixdata-sources' into 'master'Emmanuele Bassi2018-09-131-1/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | build: Include gdk-pixdata.c when building GdkPixbuf-2.0.gir Closes #92 See merge request GNOME/gdk-pixbuf!17
| * | | 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
* | | Merge branch 'basename' into 'master'Emmanuele Bassi2018-09-092-2/+2
|\ \ \ | |/ / |/| | | | | | | | Use @basename@ instead of @filename@ for reproducible builds See merge request GNOME/gdk-pixbuf!15
| * | Use @basename@ instead of @filename@ for reproducible buildsChris Lamb2018-09-092-2/+2
|/ / | | | | | | | | | | | | | | | | | | | | | | | | Whilst working on the Reproducible Builds effort [0], we noticed [1] that gdk-pixbuf could not be built reproducibly as it includes the absolute build path. The glib-mkenums documentation recommends using @basename@ over @filename@ for this reason [2]. [0] https://reproducible-builds.org/ [1] https://bugs.debian.org/908309 [2] https://developer.gnome.org/gobject/stable/glib-mkenums.html#id-1.5.2.5.4
* | Merge branch 'png-faster' into 'master'Emmanuele Bassi2018-09-061-1/+1
|\ \ | | | | | | | | | | | | | | | | | | Speed up saving PNGs by skipping a null transform Closes #90 See merge request GNOME/gdk-pixbuf!14
| * | Speed up saving PNGs by skipping a null transformBrion Vibber2018-09-061-1/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Calling png_set_shift to set the number of significant bits of input triggers a transform operation inside libpng which shifts bits around, even if it's a null operation of 8 bits to 8 bits. I measured this slowdown as about 30% of total saving runtime on a large 7680x2160 screenshot. In addition, only 8 bits per channel are supported in gdk-pixbuf so this is never actually needed in practice... Skipping the png_set_shift call altogether doesn't change output and speeds it up nicely. Fixes #90
* | Update Belarusian translationYuras Shumovich2018-09-061-140/+139
| |
* | Merge branch 'issue-88' into 'master'Emmanuele Bassi2018-09-051-0/+4
|\ \ | |/ |/| | | | | | | | | Ensure that building loaders.cache depends on modules Closes #88 See merge request GNOME/gdk-pixbuf!13
| * 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
* Release GdkPixbuf 2.38.02.38.0Emmanuele Bassi2018-09-012-1/+5
|
* Use the appropriate version for unavailable annotationsEmmanuele Bassi2018-09-011-7/+7
| | | | | | | | A copy and paste thinko on the GDK_PIXBUF_UNAVAILABLE_IN_* macros after 2.22 generated the exact same warning for all releases after that. This commit introduces no functional change, only an updated compiler warning with the correct version numbers.
* docs: Add missing symbol index for 2.38Emmanuele Bassi2018-09-011-0/+4
|
* docs: Re-organise the API reference indexEmmanuele Bassi2018-09-011-9/+19
| | | | | Group the sections that are deprecated or that defer to another library, to ensure that readers are aware of their status at a glance.
* Add missing 2.38 versioning macrosEmmanuele Bassi2018-09-012-0/+29
| | | | | We did not introduce any new symbol, but it's good project hygiene to always have per-release version macros as part of the release process.
* docs: Fix the link to the GDK referenceEmmanuele Bassi2018-09-012-15/+6
| | | | We need to use the ulink element, not the link one, for URLs.
* Remove gdk-pixbuf.typesEmmanuele Bassi2018-09-011-7/+0
| | | | | We regenerate the types file every time we build the documentation, to avoid missing types.
* docs: Style fixes for the READMEEmmanuele Bassi2018-08-301-9/+9
| | | | A couple clarifications of the wording in the build instruction.
* docs: Link to the dependenciesEmmanuele Bassi2018-08-301-6/+6
| | | | Make the README a bit more helpful.
* Release gdk-pixbuf 2.37.922.37.92Emmanuele Bassi2018-08-222-1/+6
|
* Documentation fixes for read_pixels() and read_pixels_bytes()Emmanuele Bassi2018-08-221-4/+11
| | | | | | | | | The read_pixels() method is missing a `Returns` stanza. The read_pixels_bytes() method is missing a description. Both functions do the same thing, so they should be documented similarly.
* Require Meson ≥ 0.46Emmanuele Bassi2018-08-221-6/+2
| | | | | Drop the conditional support on get_supported_link_arguments(), as there have been multiple stable releases of Meson with that method.
* Merge branch 'clarify-pixels-bytes' into 'master'Emmanuele Bassi2018-08-2222-203/+373
|\ | | | | | | | | Clarify pixels vs. bytes See merge request GNOME/gdk-pixbuf!6
| * Coding style fixupsFederico Mena Quintero2018-07-012-13/+13
| |
| * README.md: notes on how to specify build options and run the test suiteFederico Mena Quintero2018-06-011-0/+21
| |
| * io-jasper.c: Don't use gdk-pixbuf-private.hFederico Mena Quintero2018-06-011-2/+3
| |
| * io-jpeg.c: Don't use gdk-pixbuf-private.hFederico Mena Quintero2018-06-011-5/+5
| |
| * io-pnm.c: Don't use gdk-pixbuf-private.hFederico Mena Quintero2018-06-011-3/+4
| |
| * io-gif.c: Don't use gdk-pixbuf-private.hFederico Mena Quintero2018-06-011-1/+2
| |
| * io-qtif.c: Don't use gdk-pixbuf-private.hFederico Mena Quintero2018-06-011-1/+1
| |
View Lorry Controller Status