*** empty log message ***
[bpt/emacs.git] / INSTALL-CVS
CommitLineData
e0156c8d
EZ
1 Building and Installing Emacs from CVS
2
3Some of the files that are included in the Emacs tarball, such as
4byte-compiled Lisp files, are not stored in the CVS repository.
5Therefore, to build from CVS you must run "make bootstrap"
6instead of just "make":
7
8 $ ./configure
9 $ make bootstrap
10
11The bootstrap process makes sure all necessary files are rebuilt
12before it builds the final Emacs binary.
13
14Normally, it is not necessary to use "make bootstrap" after every CVS
15update. Unless there are problems, we suggest the following
16procedure:
17
18 $ ./configure
19 $ make
20 $ cd lisp
21 $ make recompile EMACS=../src/emacs
22 $ cd ..
23 $ make
24
25(If you want to install the Emacs binary, type "make install" instead
26of "make" in the last command.)
27
28If the above procedure fails, try "make bootstrap".
29
30Users of non-Posix systems (MS-Windows etc.) should run the
31platform-specific configuration scripts (nt/configure.bat, config.bat,
32etc.) before "make bootstrap" or "make"; the rest of the procedure is
33applicable to those systems as well.
34
35Note that "make bootstrap" overwrites some files that are under CVS
36control, such as lisp/loaddefs.el. This could produce CVS conflicts
37next time that you resync with the CVS. If you see such conflicts,
38overwrite your local copy of the file with the clean version from the
39CVS repository. For example:
40
41 cvs update -C lisp/loaddefs.el
42
43Please report any bugs in the CVS versions to emacs-pretest-bug@gnu.org.