Moving homebrewn binaries and question about building documentation

Moving homebrewn binaries and question about building documentation

[Eric Lilja]

Hi!

I just built emacs on Windows XP Pro SP2 with the following script:
#!/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?

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)?

If I look at the official emacs windows binaries that directory contains 
only bin, etc, info, leim, lisp, and sitelisp subdirectories and a few 
top-level readmes. As a result, it's several megabytes smaller. Just 
remove the directories that are not in the offical binary package and 
that's that?

Any replies welcome.

- Eric

Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii]

> 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.

Re: Moving homebrewn binaries and question about building documentation

[Eric Lilja]

Eli Zaretskii wrote:
>> 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.

Ah, thanks for the useful reply, Eli! I've changed my script to:
#!/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 info
mingw32-make install INSTALL_DIR=c:/emacs/

and I'm going to test it now (builds are started in 
c:/cvsemacs/emacs/nt) and no more manual copy to c:/emacs if this works 
or wondering what to copy.

I actually wrote an application that cleaned the emacs tree from the 
CVS-dirs but then that one is not needed anymore now that you've armed 
me with this new information! Thanks! :) I will post back if I encounter 
any problems.

- Eric

Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii]

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Sat, 21 Jul 2007 16:32:49 +0200
> 
> Thanks! :) I will post back if I encounter any problems.

Thanks in advance.

Re: Moving homebrewn binaries and question about building documentation

[Eric Lilja]

Eric Lilja wrote:
> Eli Zaretskii wrote:
>>> 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.
> 
> Ah, thanks for the useful reply, Eli! I've changed my script to:
> #!/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 info
> mingw32-make install INSTALL_DIR=c:/emacs/
> 
> and I'm going to test it now (builds are started in 
> c:/cvsemacs/emacs/nt) and no more manual copy to c:/emacs if this works 
> or wondering what to copy.
> 
> I actually wrote an application that cleaned the emacs tree from the 
> CVS-dirs but then that one is not needed anymore now that you've armed 
> me with this new information! Thanks! :) I will post back if I encounter 
> any problems.
> 
> - Eric

Ok, I just ran the script in my previous reply. There were a few 
"problems". As you can see I had a trailing / in my INSTALL_DIR so 
install tries to copy like this (just pasting one example):
cp -f oo-spd/i386/etags.exe c:/emacs//bin
Notice the double forward slash. It didn't seem to affect copying, 
though, and I will simply remove the trailing slash from INSTALL_DIR in 
my script (I thought it would check for a trailing slash and add one if 
there wasn't one but it seems it adds one regardless).
Also, I still have many CVS directories in the subdirectories. I also 
noticed two empty top-level directories named lock and data, 
respectively. These are not present in the official emacs 22.1 windows 
binary package. Comments?

- Eric

Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii]

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Sat, 21 Jul 2007 16:56:00 +0200
> 
> As you can see I had a trailing / in my INSTALL_DIR so 
> install tries to copy like this (just pasting one example):
> cp -f oo-spd/i386/etags.exe c:/emacs//bin
> Notice the double forward slash. It didn't seem to affect copying, 
> though, and I will simply remove the trailing slash from INSTALL_DIR in 
> my script (I thought it would check for a trailing slash and add one if 
> there wasn't one but it seems it adds one regardless).

This is not a problem, as you've found out, but it's better to not
have a trailing slash in INSTALL_DIR.

> Also, I still have many CVS directories in the subdirectories.

Only in etc/ and leim/.  The Unix "make install" removes them after
copying (see the `install:' target in the top-level Makefile.in), but
the Windows build does not want to rely on the utilities required for
that.  If you have them, you can remove those after "make install"
finishes.

> I also 
> noticed two empty top-level directories named lock and data, 
> respectively. These are not present in the official emacs 22.1 windows 
> binary package. Comments?

These are created by two explicit lines in nt/makefile, but I don't
know why.  Anybody?

Re: Moving homebrewn binaries and question about building documentation

[Eric Lilja]

Eli Zaretskii wrote:
>> From: Eric Lilja <mindcooler@gmail.com>
>> Date: Sat, 21 Jul 2007 16:56:00 +0200
>>
>> As you can see I had a trailing / in my INSTALL_DIR so 
>> install tries to copy like this (just pasting one example):
>> cp -f oo-spd/i386/etags.exe c:/emacs//bin
>> Notice the double forward slash. It didn't seem to affect copying, 
>> though, and I will simply remove the trailing slash from INSTALL_DIR in 
>> my script (I thought it would check for a trailing slash and add one if 
>> there wasn't one but it seems it adds one regardless).
> 
> This is not a problem, as you've found out, but it's better to not
> have a trailing slash in INSTALL_DIR.

I hear you. I have fixed my script in this regard and added a comment
about it should I forget it.

> 
>> Also, I still have many CVS directories in the subdirectories.
> 
> Only in etc/ and leim/.  The Unix "make install" removes them after
> copying (see the `install:' target in the top-level Makefile.in), but
> the Windows build does not want to rely on the utilities required for
> that.  If you have them, you can remove those after "make install"
> finishes.

And info as well, anyway, what I wanted to do was not to nitpick but ask 
you if you know of a clever way I can remove these directories from 
inside my script? It's a bash script run under cygwin bash. I'm not 
really a unix person, so I don't know what I'm talking about here, but 
maybe something involving find and rm? If I can get rid of my standalone 
application for removing these directories and incorporate its 
functionality in my cvs build script, that would be nice.

> 
>> I also 
>> noticed two empty top-level directories named lock and data, 
>> respectively. These are not present in the official emacs 22.1 windows 
>> binary package. Comments?
> 
> These are created by two explicit lines in nt/makefile, but I don't
> know why.  Anybody?

I will leave them untouched for now, but if they are not needed it would 
be nice if they were not created, of course.

You're a great asset, Eli! Thanks!

- Eric

Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii]

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Sat, 21 Jul 2007 18:25:30 +0200
> 
> if you know of a clever way I can remove these directories from 
> inside my script?

Just copy these lines from Makefile.in:

	      for subdir in `find $${dest} -type d ! -name RCS ! -name CVS -print` ; do \
		chmod a+rx $${subdir} ; \
		rm -rf $${subdir}/RCS ; \
		rm -rf $${subdir}/CVS ; \
		rm -f  $${subdir}/.cvsignore ; \
		rm -f  $${subdir}/.arch-inventory ; \
		rm -f  $${subdir}/\#* ; \
		rm -f  $${subdir}/.\#* ; \
		rm -f  $${subdir}/*~ ; \
		rm -f  $${subdir}/*.orig ; \
		rm -f  $${subdir}/[mM]akefile* ; \
		rm -f  $${subdir}/ChangeLog* ; \
		rm -f  $${subdir}/dired.todo ; \
	      done) ; \

where $$(dest) is the value of INSTALL_DIR you give to "make install".

(You will have to convert $$ into $ in this snippet, for it to work
from a script, as opposed to a Makefile.)

> You're a great asset, Eli! Thanks!

You're welcome.

Re: Moving homebrewn binaries and question about building documentation

[Eric Lilja]

Eli Zaretskii wrote:
>> From: Eric Lilja <mindcooler@gmail.com>
>> Date: Sat, 21 Jul 2007 18:25:30 +0200
>>
>> if you know of a clever way I can remove these directories from 
>> inside my script?
> 
> Just copy these lines from Makefile.in:
> 
> 	      for subdir in `find $${dest} -type d ! -name RCS ! -name CVS -print` ; do \
> 		chmod a+rx $${subdir} ; \
> 		rm -rf $${subdir}/RCS ; \
> 		rm -rf $${subdir}/CVS ; \
> 		rm -f  $${subdir}/.cvsignore ; \
> 		rm -f  $${subdir}/.arch-inventory ; \
> 		rm -f  $${subdir}/\#* ; \
> 		rm -f  $${subdir}/.\#* ; \
> 		rm -f  $${subdir}/*~ ; \
> 		rm -f  $${subdir}/*.orig ; \
> 		rm -f  $${subdir}/[mM]akefile* ; \
> 		rm -f  $${subdir}/ChangeLog* ; \
> 		rm -f  $${subdir}/dired.todo ; \
> 	      done) ; \
> 
> where $$(dest) is the value of INSTALL_DIR you give to "make install".
> 
> (You will have to convert $$ into $ in this snippet, for it to work
> from a script, as opposed to a Makefile.)
> 
>> You're a great asset, Eli! Thanks!
> 
> You're welcome.

Thanks again, Eli. I decided to settle for just removing the CVS-subdir, 
for now. My script now looks like this:
#!/bin/bash
export CVS_RSH="ssh"
touch ~/.cvspass
#cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs co emacs
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 info

# Don't have a trailing / in INSTALL_DIR because one will be added 
regardless.
# mingw32-make install will remove some CVS-directories on Windows, not all.
# Note: No spaces surrounding the = !
INSTDIR=c:/emacs

mingw32-make install INSTALL_DIR=$INSTDIR

# On Windows, some CVS-directories are left in the installation dir.
# The following code snippet removes them.
for subdir in `find $INSTDIR -type d ! -name RCS ! -name CVS -print` ; do \
     rm -rf $subdir/CVS;
done ;

It seems to do what I want, the CVS directories seem to be gone. Looks OK?

- Eric

Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii]

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Sat, 21 Jul 2007 19:37:29 +0200
> 
> It seems to do what I want, the CVS directories seem to be gone. Looks OK?

Yep.

Re: Moving homebrewn binaries and question about building documentation

[dhruva]

Hi,

On 7/21/07, Eric Lilja <mindcooler@gmail.com> wrote:
> inside my script? It's a bash script run under cygwin bash. I'm not
> really a unix person, so I don't know what I'm talking about here, but

Since you want to have your script run in a windows environment, would
you like it to be a 'bat' file instead of a bash shell script? I have
a decent (enough to implement) knowledge of both bash and DOS command
scripting. I can help.

As a hobby, I am trying to implement "rm -fr", "mkdir -p", "find
-exec" and other UNIX tools as pure windows batch files in the hope of
having a pure windows build and install for Emacs (with out any
external dependencies).

-dky

-- 
Dhruva Krishnamurthy
Contents reflect my personal views only!

Re: Moving homebrewn binaries and question about building documentation

[Eric Lilja]

dhruva wrote:
> Hi,
> 
> On 7/21/07, Eric Lilja <mindcooler@gmail.com> wrote:
>> inside my script? It's a bash script run under cygwin bash. I'm not
>> really a unix person, so I don't know what I'm talking about here, but
> 
> Since you want to have your script run in a windows environment, would
> you like it to be a 'bat' file instead of a bash shell script? I have
> a decent (enough to implement) knowledge of both bash and DOS command
> scripting. I can help.
> 
> As a hobby, I am trying to implement "rm -fr", "mkdir -p", "find
> -exec" and other UNIX tools as pure windows batch files in the hope of
> having a pure windows build and install for Emacs (with out any
> external dependencies).
> 
> -dky
> 

Not really, this is for personal use and I always use cygwin, thanks 
anyway. Others may be interested, of course.

Re: Moving homebrewn binaries and question about building documentation

[Jason Rumney]

Eli Zaretskii wrote:
>> noticed two empty top-level directories named lock and data, 
>> respectively.
>>     
>
> These are created by two explicit lines in nt/makefile, but I don't
> know why.  Anybody?
>   


A throwback to when they used to be required (Emacs 19.x?)

Re: Moving homebrewn binaries and question about building documentation

[Eli Zaretskii]

> Date: Sat, 21 Jul 2007 23:17:43 +0100
> From: Jason Rumney <jasonr@gnu.org>
> Cc: Eric Lilja <mindcooler@gmail.com>, emacs-devel@gnu.org
> 
> Eli Zaretskii wrote:
> >> noticed two empty top-level directories named lock and data, 
> >> respectively.
> >>     
> >
> > These are created by two explicit lines in nt/makefile, but I don't
> > know why.  Anybody?
> 
> A throwback to when they used to be required (Emacs 19.x?)

In that case, we should just delete them.

Re: Moving homebrewn binaries and question about building documentation

[Eric Lilja]

Eli Zaretskii wrote:
>> Date: Sat, 21 Jul 2007 23:17:43 +0100
>> From: Jason Rumney <jasonr@gnu.org>
>> Cc: Eric Lilja <mindcooler@gmail.com>, emacs-devel@gnu.org
>>
>> Eli Zaretskii wrote:
>>>> noticed two empty top-level directories named lock and data, 
>>>> respectively.
>>>>     
>>> These are created by two explicit lines in nt/makefile, but I don't
>>> know why.  Anybody?
>> A throwback to when they used to be required (Emacs 19.x?)
> 
> In that case, we should just delete them.

Yes! :)