Re: Build error: "nmake info" in "emacs/man"

[Eli Zaretskii]

> Cc: address@hidden, address@hidden, address@hidden
> From: Reiner Steib <address@hidden>
> Date: Thu, 09 Sep 2004 12:44:12 +0200
> 
> > No, I mean the fact that "cd ${srcdir}" was omitted from the commands
> > that build the Info manuals.
> 
> But "cd ${srcdir}" isn't present for the other entries neither:
> 
> --8<---------------cut here---------------start------------->8---
> $(infodir)/pcl-cvs: pcl-cvs.texi
>       $(MAKEINFO) pcl-cvs.texi
> pcl-cvs.dvi: pcl-cvs.texi
>       $(ENVADD) $(TEXI2DVI) $(srcdir)/pcl-cvs.texi
> --8<---------------cut here---------------end--------------->8---

There's no need for srcdir in the rules that produce DVI files: those
files are not installed by "make install", so they are produced in
place, even if that is outside the source tree.  By contrast, Info
files _must_ be inside the source tree, because that is where "make
install" looks for them.  You will see that the original file
man/Makefile.in, from which makefile.w32-in was copied, does that on
Unix as well.

> "cd ${srcdir}" was erroneously introduced by me when adding sieve and
> pgg (more or less C&P from Makefile.in).  There was no "cd ${srcdir}"
> in revision 1.11 of Makefile.w32-in.  If building outside of the
> source tree doesn't work now, it most probably didn't work before (<=
> 1.11) neither, AFAICS.

The question is: does the Windows build support building outside the
source tree in the other directories?  If it doesn't, then I won't
object removing the "cd ." thing in man/makefile.w32-in.  But if a
build outside the source tree _is_ supported in `src' and `lisp'
directories, then I think we should fix `man' to support it as well.