aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/snippets
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2022-05-07 23:10:13 -0400
committerEli Schwartz <eschwartz@archlinux.org>2022-05-29 18:23:03 -0400
commit915a468ed32feb5bed2bd4e60fefc5754e961a6c (patch)
tree98e7a4659ae9bc56c98d1315daa0ae26e0152674 /docs/markdown/snippets
parentde2c091ba6385af05b9556acd4daa06af9216ca3 (diff)
downloadmeson-915a468ed32feb5bed2bd4e60fefc5754e961a6c.zip
meson-915a468ed32feb5bed2bd4e60fefc5754e961a6c.tar.gz
meson-915a468ed32feb5bed2bd4e60fefc5754e961a6c.tar.bz2
i18n: be build-compatible (but not developer-compatible) with gettext-tiny
For maintainer targets, we need some more tools that gettext-tiny doesn't implement. It's a shame to cause NLS to be completely disabled in such environments, so instead just issue a warning and continue. Before 0.62.0 these were never checked for, and would simply fail at runtime, probably. In theory, the user might install the tools in between configuring and building, and then the maintainer targets would begin to work. Return to that behavior -- we still create the targets, which will *probably* fail, but might not -- and for existing integrations, failing at `ninja foo-update-po` with "error, program msgmerge not found" is a bit more discoverable than ninja saying "what do you mean, there's no such target". We still have the 0.62.0 preferred behavior of trying to find the programs, succeeding in all cases other than gettext-tiny, and guaranteeing that their paths are set up in a machine-file-respecting manner.
Diffstat (limited to 'docs/markdown/snippets')
0 files changed, 0 insertions, 0 deletions