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

Include libspng as dependency #50

Merged
merged 1 commit into from
Aug 10, 2020
Merged

Include libspng as dependency #50

merged 1 commit into from
Aug 10, 2020

Conversation

kleisauke
Copy link
Collaborator

In line with the Windows binaries. I've backported randy408/libspng@b21b214 to help libvips/libvips#1748.

@lovell lovell merged commit de1ceab into lovell:master Aug 10, 2020
@lovell
Copy link
Owner

lovell commented Aug 10, 2020

Brilliant, thank you.

@kleisauke kleisauke deleted the libspng branch August 11, 2020 12:16
@kleisauke
Copy link
Collaborator Author

Perhaps randy408/libspng@db86b2c should also be backported? See: libvips/libvips#1778.

@lovell
Copy link
Owner

lovell commented Aug 23, 2020

I'm keen to release sharp v0.26.0 (plus the new statically-linked libvips 8.10.0). The switch to static linking should allow for more frequent releases of the prebuilt libvips binaries, plus we can bump these in patch version increments of sharp.

@kleisauke
Copy link
Collaborator Author

Great! These patches are no longer needed when libspng v0.6.1 is released (which will soon be released, I think).

@lovell
Copy link
Owner

lovell commented Aug 23, 2020

Ah, I've just followed the trail of randy408/libspng#123 and given it's possible for libpng+libvips to create PNG images that libspng cannot then read back again, maybe we should backport this now.

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.

2 participants