Re: gettext

[Daiki Ueno <ueno gnu org>]

Patrick Welche <prlw1 cam ac uk> writes:

> Another surprise:
>
> $ autoreconf -vif
> ...
> $ mkdir obj
> $ cd obj
> $ ../configure
> ...
> $ cd po
> $ ls
> Makefile     Makefile.in  POTFILES
> $ make cs.gmo
> cd ../../po && rm -f cs.gmo && /usr/bin/msgfmt -c --statistics
> --verbose -o cs.gmo cs.po
> 250 translated messages.
> $ ls
> Makefile     Makefile.in  POTFILES
> $ ls ../../po/cs.gmo
> ../../po/cs.gmo
>
> Problem is, the Makefile.in.in comes from gettext 19.8.1 so fiddling to
> use objdir is "interesting".
>
> Non-source tree builds impossible?

I haven't checked other implementations yet, but I would say that the
behaviour is normal, at least in the context of automake:
http://www.gnu.org/software/automake/manual/automake.html#VPATH-Builds
  [...]
     The build tree is rooted in the directory in which ‘configure’ was
  run, and is populated with all object files, programs, libraries, and
  other derived files built from the sources (and _hence not distributed_).

Since .gmo files are distributed, like ./configure, .info files, or Vala
generated .c files, they should be generated in $srcdir, rather than
$builddir.

Regards,
-- 
Daiki Ueno