summaryrefslogtreecommitdiff
path: root/INSTALL.REPO
diff options
context:
space:
mode:
authorStephen Leake <stephen_leake@stephe-leake.org>2014-12-06 02:11:36 -0600
committerStephen Leake <stephen_leake@stephe-leake.org>2014-12-06 02:38:34 -0600
commit06264b3d247b21be627d1bcd7d928cd3140d249a (patch)
treed47798b293468d4a60a185f4c62e2cda64601627 /INSTALL.REPO
parent7841e9348276c076eb6be26683ee25f0e0db4706 (diff)
downloademacs-06264b3d247b21be627d1bcd7d928cd3140d249a.tar.gz
Improve CONTRIBUTE and related files.
* CONTRIBUTE: improve; add explicit web references, move some info from admin/notes/* here. * INSTALL.REPO: You can't "just run make" after a clean checkout. * admin/notes/commits: deleted; merged into ./CONTRIBUTE * admin/notes/repo: move commit, branch info into ./CONTRIBUTE
Diffstat (limited to 'INSTALL.REPO')
-rw-r--r--INSTALL.REPO11
1 files changed, 6 insertions, 5 deletions
diff --git a/INSTALL.REPO b/INSTALL.REPO
index 83b6f2f4133..67dceb8c6eb 100644
--- a/INSTALL.REPO
+++ b/INSTALL.REPO
@@ -1,10 +1,5 @@
Building and Installing Emacs from the Repository
-Simply run 'make'. This should work if your files are freshly checked
-out from the repository, and if you have the proper tools installed.
-If it doesn't work, or if you have special build requirements, the
-following information may be helpful.
-
Building Emacs from the source-code repository requires some tools
that are not needed when building from a release. You will need:
@@ -34,6 +29,12 @@ can invoke './configure -C'. After configuring, build Emacs as follows:
If you want to install Emacs, type 'make install' instead of 'make' in
the last command.
+After your first build, you can usually just run 'make' after any
+updates from the Savannah repository or local edits; the makefile
+contains logic to re-run configure as needed. However, if the autoconf
+input files have changed, or in some other situations, you will need
+to run 'make bootstrap' (more below).
+
Occasionally the file 'lisp/loaddefs.el' (and similar automatically
generated files, such as 'esh-groups.el', and '*-loaddefs.el' in some
subdirectories of 'lisp/', e.g., 'mh-e/' and 'calendar/') will need to be