From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Making a script to update and compile from CVS
Date: Fri, 14 Jan 2005 12:39:27 +0000 (UTC) [thread overview]
Message-ID: <m1CpQjf-0004RAC@rattlesnake.com> (raw)
"Lennart Borgman" <lennart.borgman.073@student.lu.se> wrote
> I saw someone made a try on EmacsWiki to automate the process of
> copying and building Emacs from CVS.
Here is what I do:
;; Each day, as user `bob' in an instance of Emacs, I run this for CVS
;; updates:
(progn
(cd "/usr/local/src/emacs/")
(cvs-update "/usr/local/src/emacs/" t))
;; Next, I run the fast `make recompile' command.
;; The `make recompile' command recompiles all Lisp files which are
;; new; it does not create .elc files. It only recompiles a file if
;; an .elc is already present.
(progn
(cd "/usr/local/src/emacs/")
(compile
"time make -C lisp autoloads && cd lisp && \
time make recompile \
EMACS=/usr/local/src/emacs/src/emacs && \
cd /usr/local/src/emacs/ && \
time make info html"))
;; (Once in a while I rebuild the DVI documentation by running
;; `make info html dvi'.)
;; Occasionally, I run the `bootfast' command which recompiles all the
;; Emacs Lisp files. I have been warned that sometimes an old .elc
;; file will cause trouble, but that has not happened yet. Also, this
;; command deletes many other files. This command takes a long time.
(progn
(cd "/usr/local/src/emacs/")
(compile "date && time make bootfast"))
;; Finally, once in a great while, I configure and run `make bootstrap'
;; This takes a long time.
(progn
(cd "/usr/local/src/emacs/")
(compile
"./configure --with-type1 \
--with-x-toolkit=gtk --with-pop \
--prefix=/usr/local --with-sound=yes \
&& time make bootstrap"))
;; I have not had to update autoloads for months or maybe years, but
;; when I did, I used this command:
(progn
(cd "/usr/local/src/emacs/lisp/")
(compile "make autoloads EMACS=../src/emacs"))
;; For installation, I run the following in a root owned instance of Emacs:
(progn (cd "/usr/local/src/emacs/") (compile "time make install"))
;; To make tags, which I do occasionally:
(progn (cd "/usr/local/src/emacs/") (compile "time make TAGS"))
--
Robert J. Chassell
bob@rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.rattlesnake.com http://www.teak.cc
next reply other threads:[~2005-01-14 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 12:39 Robert J. Chassell [this message]
2005-01-14 18:58 ` Making a script to update and compile from CVS Vinicius Jose Latorre
2005-01-14 21:40 ` Michael Albinus
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 21:36 Lennart Borgman
2005-01-13 23:34 ` Miles Bader
2005-01-15 0:12 ` Richard Stallman
2005-01-13 23:38 ` Stefan Monnier
2005-01-14 10:26 ` Kai Großjohann
2005-01-14 19:39 ` Han Boetes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1CpQjf-0004RAC@rattlesnake.com \
--to=bob@rattlesnake.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).