-
Notifications
You must be signed in to change notification settings - Fork 561
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
[Harfbuzz] update to 8.3.1 #8392
Conversation
For the benefit of future (and current) readers, the error is
I guess one option is to not request CoreText explicitly? Another option is to read the relevant log and understand why meson claims the CoreText framework isn't available. |
Disabling CoreText causes segfaults (disabling it in Pango and/or Cairo would probably prevent that, but I think it's important and we should try to keep it). From the log:
I don't know how to fix the error, but patching meson.build to bypass the check does fix the MacOS build. Fixing it is obviously preferrable but maybe this is OK for now? Cf #8497, do we need to add a compat for Cairo_jll and other dependencies? |
Is this good to go now? |
I think so -- for this to be used we'll have to rebuild Pango_jll and libass_jll since their compat is set for the old version. |
Why? |
Maybe I'm wrong, but I had to modify the compat in the JLL's to test them locally, otherwise they wouldn't install. Anyway, the answer to your original question is "yes". |
Ah, I see, we're jumping from v2.8.1 to v8.3.1. And there's already v9.0.0 |
Thanks for merging -- yes newer versions including 9 are available but I thought it might be smart to wait for 9.x because these font libraries often seem problematic. |
Updating HarfBuzz and enabling GDI and DWrite fixes font issues on Windows:
JuliaGtk/Gtk4.jl#32
JuliaGtk/Gtk4.jl#42
JuliaGraphics/Cairo.jl#349
I haven't a clue how to fix the Mac build.Bypassing a broken check for CoreText support lets the Mac build go ahead, and I have verified locally that the JLL works on my Mac.Also, because of the huge version jump there may be compatibility issues with JLL's that depend on HarfBuzz. The soname hasn't changed, but: harfbuzz/harfbuzz#3216. I don't actually think this is an issue, since the API's that changed were experimental and not likely used by the libraries in Yggdrasil.