1. 16 Apr, 2021 1 commit
  2. 21 Mar, 2021 2 commits
  3. 09 Feb, 2021 1 commit
  4. 10 Nov, 2020 1 commit
  5. 26 Jun, 2020 1 commit
    • Emmanuele Bassi's avatar
      Remove the libjasper-based JPEG2000 loader · 4a278c66
      Emmanuele Bassi authored
      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
      4a278c66
  6. 07 Jan, 2020 1 commit
  7. 14 Aug, 2019 1 commit
  8. 05 Mar, 2019 1 commit
    • Bastien Nocera's avatar
      core: Always initialise default pixbuf loaders · bc02d8e4
      Bastien Nocera authored and Emmanuele Bassi's avatar Emmanuele Bassi committed
      The "run once" initialisation of pixbuf modules shipped with gdk-pixbuf
      itself would be skipped if an application was successfully calling
      gdk_pixbuf_init_modules() first, as this would set the internal list of
      file_formats to be non-NULL, and skip any initialisation of those
      modules.
      
      This fix makes sure that pixbuf modules shipped with gdk-pixbuf are
      always initialised, regardless of whether gdk_pixbuf_init_modules()
      successfully initialised an application provided one.
      
      Fixes: fd1376b7
      bc02d8e4
  9. 28 Feb, 2019 3 commits
  10. 29 Apr, 2018 1 commit
    • Emmanuele Bassi's avatar
      Avoid a compiler warning · c975e024
      Emmanuele Bassi authored
      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.
      c975e024
  11. 24 Apr, 2018 1 commit
    • Christoph Reiter's avatar
      windows: rework loaders cache relocation support · 6ef31828
      Christoph Reiter authored
      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
      6ef31828
  12. 08 Jan, 2018 1 commit
  13. 30 Dec, 2017 1 commit
  14. 08 Dec, 2017 1 commit
  15. 05 Dec, 2017 1 commit
  16. 20 Nov, 2017 2 commits
  17. 27 Jul, 2017 1 commit
  18. 12 Jul, 2017 2 commits
  19. 07 Feb, 2017 1 commit
  20. 28 Dec, 2016 2 commits
  21. 19 Dec, 2016 1 commit
  22. 13 Dec, 2016 1 commit
  23. 07 Nov, 2016 1 commit
  24. 02 Aug, 2016 2 commits
  25. 06 Apr, 2016 1 commit
  26. 25 Sep, 2015 1 commit
  27. 25 Aug, 2015 1 commit
  28. 23 Aug, 2015 1 commit
  29. 30 Apr, 2015 1 commit
  30. 05 Mar, 2015 1 commit
  31. 21 Nov, 2014 1 commit
  32. 23 Oct, 2014 2 commits