emo/procps
1
0
Fork 0
Code Issues Pull Requests Packages Releases Activity
1f74877096
procps/man-po/Makefile.am

118 lines
3.0 KiB
Makefile
Raw Normal View History

Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
build-sys: Use po4a for manpage translations Using the newer po4a tool for manpage translations. Also removing the manpage po file update from dist target because it should be something the is explicitly done. The git repository will hold the original man pages and the po translation files. The distribution tarball will hold those and the translated manpages. This means most people won't need po4a as the distribution fill will have these translated manpages.
2019-11-11 16:11:00 +05:30
# *.po and *.pot are kept in VCS and generated by po4a-dist command
# translated/* are put in distribution but not found in VCS
#
# run:
# make -C man-po po4a-dist
# To update man page translations
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
dist_man_MANS = \
../free.1 \
../pgrep.1 \
../pkill.1 \
../pmap.1 \
../uptime.1 \
../vmstat.8 \
../w.1 \
../ps/procps.1
if !CYGWIN
dist_man_MANS += \
../pwdx.1 \
../tload.1 \
../sysctl.8 \
../sysctl.conf.5 \
../ps/ps.1
endif
docs: more Makefile updates The install target was using the wrong directory and would throw some errors where a language couldn't translate man pages. This one should be hopefully more robust.
2019-11-12 15:45:33 +05:30
translated_MANS = $(wildcard translated/*/*.[1-9])
translated_MAN_sections=$(subst .,,$(sort $(suffix $(translated_MANS))))
translated_langs = $(notdir $(wildcard translated/*))
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
docs: more Makefile updates The install target was using the wrong directory and would throw some errors where a language couldn't translate man pages. This one should be hopefully more robust.
2019-11-12 15:45:33 +05:30
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
EXTRA_DIST = po4a.cfg \
procps-man.pot \
$(translated_MANS)
build-sys: One more man-po build fix
2021-01-21 16:28:48 +05:30
# Extract the list of languages from the po4a config file.
LINGUAS_DIST = $(shell sed -ne 's/^.*\[po4a_langs\] \(.*\)$$/\1/p' $(srcdir)/po4a.cfg)
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
# If the user has not defined it let's use the default.
LINGUAS ?= $(LINGUAS_DIST)
PO4A_V = $(PO4A_V_@AM_V@)
PO4A_V_ = $(PO4A_V_@AM_DEFAULT_V@)
PO4A_V_0 = @echo " PO4A $@";
PO4A_OPTS = --srcdir $(srcdir) --destdir $(CURDIR) \
--package-name $(PACKAGE) --package-version $(VERSION) \
--msgid-bugs-address "Procps list <procps@freelists.org>"
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
build-sys: Update build to install translated manpages Based on the psmisc build system this now installs the translated man pages and seems to survive a make distcheck
2021-01-21 16:10:10 +05:30
all-local: all-local-@USE_PO4A@
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
build-sys: Update build to install translated manpages Based on the psmisc build system this now installs the translated man pages and seems to survive a make distcheck
2021-01-21 16:10:10 +05:30
all-local-no:
all-local-yes: man.stamp
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
build-sys: Update build to install translated manpages Based on the psmisc build system this now installs the translated man pages and seems to survive a make distcheck
2021-01-21 16:10:10 +05:30
# FIXME: Use a stamp file until po4a supports them internally.
man.stamp:
$(PO4A_V) $(PO4A) $(PO4A_OPTS) $(srcdir)/po4a.cfg
$(AM_V_at) touch $@
clean-local: clean-local-@USE_PO4A@
clean-local-no:
clean-local-yes:
rm -rf $(LINGUAS_DIST)
$(AM_V_at) rm -f man.stamp
.PHONY: update-po
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
procps-man.pot:
# parafiles = $(patsubst %,-m%,$(subst :, ,$(dist_man_MANS)))
# parafiles = $(dist_man_MANS:doc=Ente)
po4a-gettextize -M utf8 --option groff_code=verbatim --option generated --option untranslated="a.RE,\|" --option unknown_macros=untranslated -f man $(patsubst %,-m%,$(subst :, ,$(dist_man_MANS))) -p $@
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
build-sys: Don't require po4a for installation The build system tested for the presence of po4a binary at the install step. procps ships with translated man pages so doesn't need po4a for install/uninstallation. Works already in psmisc! References: https://gitlab.com/psmisc/psmisc/-/commit/5fab6b7ab385080f1db725d6803136ec1841a15f Signed-off-by: Craig Small <csmall@dropbear.xyz>
2021-02-08 15:53:41 +05:30
install-data-local:
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
for lang in $(LINGUAS) ; do \
files=""; \
for trans in $(notdir $(dist_man_MANS)); do \
build-sys: Update build to install translated manpages Based on the psmisc build system this now installs the translated man pages and seems to survive a make distcheck
2021-01-21 16:10:10 +05:30
if [ -f $(CURDIR)/$$lang/$$trans ]; then \
files="$$files $(CURDIR)/$$lang/$$trans"; \
elif [ -f $(srcdir)/$$lang/$$trans ]; then \
files="$$files $(srcdir)/$$lang/$$trans"; \
build-sys: update man translation makefile This is based upon the Makefile.am for psmisc
2019-11-28 16:23:43 +05:30
fi; \
done; \
$(MAKE) install-man \
mandir="$(mandir)/$$lang" \
man_MANS="" \
dist_man_MANS="$$files"; \
Manpage translations in Makefiles The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
2014-06-28 19:08:13 +05:30
done
build-sys: Update build to install translated manpages Based on the psmisc build system this now installs the translated man pages and seems to survive a make distcheck
2021-01-21 16:10:10 +05:30
build-sys: Don't require po4a for installation The build system tested for the presence of po4a binary at the install step. procps ships with translated man pages so doesn't need po4a for install/uninstallation. Works already in psmisc! References: https://gitlab.com/psmisc/psmisc/-/commit/5fab6b7ab385080f1db725d6803136ec1841a15f Signed-off-by: Craig Small <csmall@dropbear.xyz>
2021-02-08 15:53:41 +05:30
uninstall-local:
build-sys: Update build to install translated manpages Based on the psmisc build system this now installs the translated man pages and seems to survive a make distcheck
2021-01-21 16:10:10 +05:30
for lang in $(LINGUAS); do \
files=""; \
for trans in $(notdir $(dist_man_MANS)); do \
if [ -f $(CURDIR)/$$lang/$$trans ]; then \
files="$$files $(CURDIR)/$$lang/$$trans"; \
elif [ -f $(srcdir)/$$lang/$$trans ]; then \
files="$$files $(srcdir)/$$lang/$$trans"; \
fi; \
done; \
$(MAKE) uninstall-man \
mandir="$(mandir)/$$lang" \
man_MANS="" \
dist_man_MANS="$$files"; \
done
dist-hook: man.stamp
cp $(srcdir)/man.stamp $(distdir)/
for lang in $(LINGUAS_DIST); do \
cp $(srcdir)/$$lang.po $(distdir); \
cp $(srcdir)/$$lang.add $(distdir); \
$(MKDIR_P) $(distdir)/$$lang; \
cp -r $(srcdir)/$$lang $(distdir)/; \
done
Reference in New Issue Copy Permalink