[Pango] Update to v1.52.2 #8497
Merged
Conversation
This file contains 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
Also, update dependency on Cairo_jll.
giordano
commented
Apr 18, 2024
| Dependency("FreeType2_jll"; compat="2.10.4"), | ||
| Dependency("FreeType2_jll"; compat="2.13.1"), |
There was a problem hiding this comment.
For the record, this is because #7454 changed the compat bound of FreeType2_jll to 2.13.1, but I have no clue of why: https://github.com/JuliaPackaging/Yggdrasil/pull/7454/files#diff-e2d8f4bfb63a6c0200a9e9beeb578adef317bf2a540738ea6b7858df24e1115fR76
Due to https://gitlab.gnome.org/GNOME/pango/-/issues/792 we can't build with versions of Glib prior to v2.69.1, despite what the check in the meson script claims.
This was referenced May 12, 2024
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.
Also, update dependency on Cairo_jll. #7454 changed the build system to the newer meson, but this changed the compatibility version in the macOS binaries, which means that libraries built against Cairo 1.16 require a compatibility version way larger than what's recorded in our builds of Cairo 1.18: JuliaGraphics/Cairo.jl#362. This is non-sense, but this is a reminder that changing build systems has a cost: most of the time they don't produce 100% compatible binaries.
For the record, the problem with the macOS compatibility arises only on macOS < 12 and
-mmacosx-version-minis set to a value < 10.14 (we use 10.12 for x86_64-darwin builds, and 11.0 for aarch64-darwin builds): https://github.com/giordano/macos-compatibility-version