HCoop / bpt / emacs.git / blame
| Commit | Line | Data |
|---|---|---|
| 067d23c9 KY |
1 | Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 |
| 2 | Free Software Foundation, Inc. | |
| 3 | See the end of the file for license conditions. | |
| 4 | ||
| 5 | ||
| 6 | Building and Installing Emacs from Bazaar | |
| 7 | ||
| 8 | If this is the first time you go through it, you'll need to configure | |
| 9 | before bootstrapping: | |
| 10 | ||
| 11 | $ ./configure | |
| 12 | ||
| 13 | Some of the files that are included in the Emacs tarball, such as | |
| 14 | byte-compiled Lisp files, are not stored in Bazaar. Therefore, to | |
| 15 | build from Bazaar you must run "make bootstrap" instead of just "make": | |
| 16 | ||
| 17 | $ bzr pull | |
| 18 | $ make bootstrap | |
| 19 | ||
| 20 | Normally, it is not necessary to use "make bootstrap" after every | |
| 21 | update from Bazaar. "make" should work in 90% of the cases and be | |
| 22 | much quicker. | |
| 23 | ||
| 24 | $ make | |
| 25 | ||
| 26 | (If you want to install the Emacs binary, type "make install" instead | |
| 27 | of "make" in the last command.) | |
| 28 | ||
| 29 | Occasionally the file "lisp/loaddefs.el" (and similar automatically | |
| 30 | generated files, such as esh-groups.el, and *-loaddefs.el in some | |
| 31 | subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be | |
| 32 | updated to reflect new autoloaded functions. If you see errors (rather | |
| 33 | than warnings) about undefined lisp functions during compilation, that | |
| 34 | may be the reason. Finally, sometimes there can be build failures | |
| 35 | related to *loaddefs.el (e.g. "required feature `esh-groups' was not | |
| 36 | provided"). In that case, follow the instructions below. | |
| 37 | ||
| 38 | To update loaddefs.el (and similar files), do: | |
| 39 | ||
| 40 | $ cd lisp | |
| 41 | $ make autoloads | |
| 42 | ||
| 43 | If either of the above partial procedures fails, try "make bootstrap". | |
| 44 | If CPU time is not an issue, the most thorough way to rebuild, and | |
| 45 | avoid any spurious problems, is always to use this method. | |
| 46 | ||
| 47 | Users of non-Posix systems (MS-Windows etc.) should run the | |
| 48 | platform-specific configuration scripts (nt/configure.bat, config.bat, | |
| 49 | etc.) before "make bootstrap" or "make"; the rest of the procedure is | |
| 50 | applicable to those systems as well. | |
| 51 | ||
| 52 | Because the Bazaar version of Emacs is a work in progress, it will | |
| 53 | sometimes fail to build. Please wait a day or so (and check the bug | |
| 54 | and development mailing list archives) before reporting such problems. | |
| 55 | In most cases, the problem is known about and is just waiting for | |
| 56 | someone to fix it. | |
| 57 | ||
| 58 | ||
| 59 | \f | |
| 60 | This file is part of GNU Emacs. | |
| 61 | ||
| 62 | GNU Emacs is free software: you can redistribute it and/or modify | |
| 63 | it under the terms of the GNU General Public License as published by | |
| 64 | the Free Software Foundation, either version 3 of the License, or | |
| 65 | (at your option) any later version. | |
| 66 | ||
| 67 | GNU Emacs is distributed in the hope that it will be useful, | |
| 68 | but WITHOUT ANY WARRANTY; without even the implied warranty of | |
| 69 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | |
| 70 | GNU General Public License for more details. | |
| 71 | ||
| 72 | You should have received a copy of the GNU General Public License | |
| 73 | along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. |