freetype, harfbuzz, freetype love triangle
Hi, The short story --- I've managed to reach a point were I couldn't launch any app depending directly/indirectly on libfreetype (including xterm) and I couldn't build opt/freetype. The long story --- I've removed/uninstalled the graphite2 package. Being a soft/nice/optional dependency of harfbuzz, I had to rebuild harfbuzz. I ignored a footprint warning about the missing hb-ft.h file, I installed the new harfbuzz and ... boom! Rebuilding the freetype package failed because harfbuzz was detected by meson, but it could not be used during the make/ninja step. Adding "-D harfbuzz=disabled" to the meson setup line allowed me to rebuild freetype (and harfbuzz after, to recover the missing ht-bt.h file). Discussion --- As freetype optionally depends on harfbuzz (which optionally depends on graphite, which depends on freetype), is it worth disabling the harfbuzz support in opt/freetype/Pkgfile if hb-ft.h doesn't exist (in order to recover from cases like mine much more easier)?
Hi, On 25.06.2022 19:40, satoco64.posiwa86@murena.io wrote:
Discussion --- As freetype optionally depends on harfbuzz (which optionally depends on graphite, which depends on freetype), is it worth disabling the harfbuzz support in opt/freetype/Pkgfile if hb-ft.h doesn't exist (in order to recover from cases like mine much more easier)?
I don't see why not. It's unfortunate to run into errors like that but it's also easy to recover from that, so I personally wouldn't disable it per se. Best regards, Tim
participants (2)
-
satoco64.posiwa86@murena.io
-
tbier@posteo.de