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