+2001-11-08 Zack Weinberg <zack@codesourcery.com>
+
+ * Makefile.in (.po.pox): Look both in srcdir and builddir
+ for $(PACKAGE).pot.
+ (po/$(PACKAGE).pot): Don't move-if-change the new potfile over
+ to the source directory.
+
2001-11-09 Ben Elliston <bje@redhat.com>
Michael Meissner <meissner@redhat.com>
Andrew MacLeod <amacleod@redhat.com>
# The new .po has to be gone over by hand, so we deposit it into
# build/po with a different extension.
+# If build/po/$(PACKAGE).pot exists, use it (it was just created),
+# else use the one in srcdir.
.po.pox:
test -d po || mkdir po
- $(MSGMERGE) $< $(srcdir)/po/$(PACKAGE).pot -o $@
+ $(MSGMERGE) $< `if test -f po/$(PACKAGE).pot; \
+ then echo po/$(PACKAGE).pot; \
+ else echo $(srcdir)/po/$(PACKAGE).pot; fi` -o $@
# This rule has to look for .gmo modules in both srcdir and
# the cwd, and has to check that we actually have a catalog
# relatively harmless since the .po files do not directly depend on it.
# Note that exgettext has an awk script embedded in it which requires a
# fairly modern (POSIX-compliant) awk.
+# The .pot file is left in the build directory.
$(PACKAGE).pot: po/$(PACKAGE).pot
po/$(PACKAGE).pot: force
test -d po || mkdir po
$(MAKE) po-generated
AWK=$(AWK) $(SHELL) $(srcdir)/po/exgettext \
$(XGETTEXT) $(PACKAGE) $(srcdir)
- $(SHELL) $(srcdir)/move-if-change $(PACKAGE).pot \
- $(srcdir)/po/$(PACKAGE).pot