meson documentations sometimes adds the space and sometimes don't and we
aren't adding it most of the times unconsciously so let's the cases and
be consistent.
'disabled' wasn't implemented for some of the features so they were
getting found even with explicit -Dfeature=disabled, this implements it.
Run the following command to test this change and check whether 'disabled'
was actually effective,
meson build -Dglib=disabled -Dgobject=disabled -Dcairo=disabled -Dfontconfig=disabled -Dicu=disabled -Dfreetype=disabled -Dintrospection=disabled -Dgtk_doc=disabled
This is useful when one wants to integrate harfbuzz into another project via
meson's subproject mechanism.
This was done in #770 but no indication of anyone is using it,
let's remove it from our meson port and we can just don't care about
it in autotools port after the migration to meson.
Meson doesn't have DISTCHECK_CONFIGURE_FLAGS like concept IIUC
and enabling them is the main thing we are doing with
distcheck flags anyway so lets turn them to auto.
Instead of passing dependencies as required we used one giant shared
dependency list containing all dependencies for every library/executable.
While this kinda works, the specified deps are also used for generating
the pkg-config files and this leads to lots of Requires.private and Libs.private
entries which aren't really needed.
This removes the "deps" array and replaces it with a few smaller ones and
makes sure the public libraries only get passed the dependencies actually
needed.
Fixes#2441
ptem, used for AAT's tracking/`trak` table is equivalent to opsz of variable fonts.
For variable AAT fonts, such as SFNS, ideally variable axis of the hb_font_t
should be set and equivalent to ptem, https://crbug.com/1005969#c37
Searches variation axes of a hb_font_t object for a specific axis first,
if not set, then tries to get default style values from different
tables of the font.
Apparently the previous version of gtk-doc was doing weird changes like 1b40da99bb and d1d9bff14c
in order to make every to have something for pushing and
now that we don't have such changes it will fail.
Alternatively we can go for `git commit --allow-empty`, guess better to
pollute history of https://github.com/harfbuzz/harfbuzz.github.io however.
Behdad Esfahbod
Ebrahim Byagowi
Khaled Hosny
Simon Cozens
Qunxin Liu
Nirbheek Chauhan
Christoph Reiter