>> What exactly do you mean with 'build option'? I would like to have >> a the possibility to select the backend at runtime so that it is >> easy to run regression tests with different backends using a single >> FontConfig library. This would need an additional (but rather >> trivial) API function, though, I guess. > > I mean a compile time option in meson, which results in preprocessor > definitions that produce different builds of FontConfig, compare > here: > https://gitlab.freedesktop.org/drott/fontconfig/-/blob/fontationsIndexing/src/fcdir.c?ref_type=heads#L88 OK. > This could be made to work as a runtime switch where FontConfig is > linked with both backends, but that increases binary size and my > assumption is FontConfig clients generally do not need switchable > backends? Correct. However, I see much benefits in such a switch being conditionally available (with another Meson option) so that people can install a 'debug version' of FontConfig that allows switching, probably via the `FC_DEBUG` environment variable. Such a feature would tremendously simplify checking real-world problems by comparing the created log files of the two different backends. Werner
