GNOME Bugzilla – Bug 694697
[PATCH] cosmetic fix for configure.ac
Last modified: 2015-04-30 15:00:14 UTC
Created attachment 237380 [details] [review] fix checking alternative backends checking pkg-config is at least version 0.9.0... yes checking for HARFBUZZ... no checking for CoreText availability... no checking for CAIRO... yes checking which cairo font backends could be used... none configure: Disabling cairo support configure: error: *** Could not enable any backends. *** Must have at least one backend to build Pango. The issue seems to be that configure does not consider the alternative backend when the first one is not there.
But! HarfBuzz is a requirement of the pangofc-based (ie. pangoft2, pangoxft, pangocairo-fc) backends.
ok, is harfbuzz a hard requirement now. if so the AC_MESSAGE([no]) part should go, so that PKG_HECK_MODULES fails if it is not present at that point already (otherwise the AC_MESSAGE([no]) should become a ':' as in my patch to not say "no" twice).
There are three ways to get a useful pango backend: * win32 + cairo-win32 * coretext + cairo-coretext * harfbuzz + fontconfig + freetype + anyof(pangoft2, pangoxft, pangocairo-ft)
okay, got it. Will simplify the patch to do the cosmetic AC_MESSAGE cleanup and will hunt for harfbuzz packages for ubuntu precise. no idea how I managed to built it in the past :/
Created attachment 237423 [details] [review] don't print "no" twice are freetype/fontconfig optional if we're on linux (have_harfbuzz)? Just wonder if it should fail if those are missing (like now) or if I should add a ", :".
HarfBuzz is a new (since August?) dependency. On Linux, to have *any* backend, you need the three of FreeType, Fontconfig, and HarfBuzz. And then Xft and cairo-ft will enable more backends if available.
Fixed!