Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libvips: update to 8.12.2 #11078

Merged
merged 2 commits into from
Mar 25, 2022
Merged

Conversation

jcupitt
Copy link
Contributor

@jcupitt jcupitt commented Mar 23, 2022

Plus:

  • update project URL
  • add support for HEIC
  • add support for AVIF
  • add support for jpeg2000
  • don't build the old vips7 API (saves a few kb)
  • remove giflib (libvips now has its own GIF reader)

Plus:

- update project URL
- add support for HEIC
- add support for AVIF
- add support for jpeg2000
- don't build the old vips7 API (saves a few kb)
- remove giflib (libvips now has its own GIF reader)
@tknerr
Copy link

tknerr commented Mar 25, 2022

Thanks @jcupitt for updating the libvips version to 8.12.2 👍🏻 ❤️

This should hopefully fix the issue we had in libvips/ruby-vips#331.

I found the binaries for this PR build are published here:
https://github.com/msys2/MINGW-packages/actions/runs/2031078489

Does anyone know if we can directly install these published artifacts directly via pacman for testing purposes? (@Biswa96 or @lazka maybe?)

@Biswa96
Copy link
Member

Biswa96 commented Mar 25, 2022

I have some doubts about the dependency changes. According to the CI output, libvips does not link with aom, libde265 etc. libraries. Are you sure about those changes?

@jcupitt
Copy link
Contributor Author

jcupitt commented Mar 25, 2022

Hi @Biswa96, thank you for looking at this.

libheif uses those libraries for HEIC and AVIF encode and decode, but you're right, they are already included in the dependencies on that package. I'll remove them from libvips.

since libheif includes them already
@Biswa96
Copy link
Member

Biswa96 commented Mar 25, 2022

Thanks for the contribution ❤️

Does anyone know if we can directly install these published artifacts directly via pacman for testing purposes?

Yes, you can but for testing only. The package is generally published within 1-3 days. Meanwhile, pending packages will appear here https://packages.msys2.org/queue. After it is added to pacman repository, the update will appear here https://packages.msys2.org/updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants