Prefer to build against libjpeg-turbo and document this. #8775
+33
−35
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
All failures are unrelated. Ready to merge with an approval. |
abadams
approved these changes
Aug 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to a schism between libjpeg and libjpeg-turbo, Homebrew and many other distributions (Ubuntu, Debian, Fedora, Firefox, Chrome, etc.) refuse to use the IJG's libjpeg. Instead, the open-source world appears to have adopted libjpeg-turbo.
The buildbots have been updated to include both libraries. When and if this is merged, I'll remove libjpeg-9f.
See: https://libjpeg-turbo.org/About/Jpeg-9
See: Homebrew/homebrew-core#107511
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717076