require freetype version at least 2.8.0#579
Merged
Merged
Conversation
madebr
approved these changes
Aug 13, 2025
madebr
left a comment
madebr
left a comment
Contributor
There was a problem hiding this comment.
If it was already broken, I'm fine with enforcing a minimum compatibility version.
slouken
approved these changes
Aug 13, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Current SDL3_ttf no longer builds against old freetype versions due
to uncontitional uses of FT_COLOR features available only in v2.5.1
and newer.
RedHat Enterprise Linux 8 (RHEL8) ships with version 2.9.1, whereas
Debian oldoldstable has 2.10.4. Therefore, setting our minimum vers
as 2.8 should satisfy everyone.
On the other hand, SDF still requires freetype >= 2.11.0 and, as it
seems, it is conditionalized in SDL3_ttf not resulting in any build
failures.
If accepted, I suggest cherry-picking it into release-3.2.x as well