Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii <eliz@gnu.org>]

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Sat, 21 Jul 2007 14:23:54 +0200
> 
> #!/bin/bash
> export CVS_RSH="ssh"
> touch ~/.cvspass
> cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs co -r 
> EMACS_22_BASE emacs
> rm ~/.cvspass
> cd emacs/nt/
> ./configure.bat --with-gcc --no-cygwin --no-debug
> mingw32-make bootstrap --jobs=2 XMFLAGS="--jobs=2"
> mingw32-make install
> mingw32-make info
> 
> The last command, mingw32-make info, was not actually in the script but 
> something I performed as an afterthought. I've had problems before with 
> my homebrewn binaries not being able to find its documentation, and 
> maybe this was the missing step?

You do need the last command on Windows, since nt/makefile will not
build the documentation by default (unlike on Unix and GNU systems).
This is because Windows users are not required to have Texinfo
installed, and we don't want to ail the build for those who don't.

> My second question is: If I want to keep only the binaries and the files 
> those binaries need, which directories should I get rid of now that the 
> build is finished (and was a success)?

I'd suggest to use the "make install" target (in nt/makefile).  If you
give it a target directory, like this:

	   	make install INSTALL_DIR=/path/to/wherever/you/want

then it will copy only the files necessary for running Emacs you built
to the named directory.  You can then remove the source tree if you
don't want to keep it, and run Emacs from the directory where you told
"make install" to put it.

The advantage of "make install" as compared to removing unneeded
directories is that some files inside the directories you do need are
not copied (e.g., the CVS/ subdirectories, the ChangeLog files, etc.).
This might result in more disk space savings.