Mercurial > emacs
diff INSTALL.BZR @ 106652:7b9e6639caa3
* INSTALL.BZR: Rename from INSTALL.CVS, edit to talk about Bazaar.
* INSTALL, autogen.sh, configure.in, configure: Adjust accordingly.
author | Karl Fogel <kfogel@red-bean.com> |
---|---|
date | Sun, 27 Dec 2009 17:26:27 -0500 |
parents | INSTALL.CVS@216634f325ab |
children | 2c3ce96392f9 |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/INSTALL.BZR Sun Dec 27 17:26:27 2009 -0500 @@ -0,0 +1,91 @@ +Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 + Free Software Foundation, Inc. +See the end of the file for license conditions. + + + Building and Installing Emacs from Bazaar + +If this is the first time you go through it, you'll need to configure +before bootstrapping: + + $ ./configure + +Some of the files that are included in the Emacs tarball, such as +byte-compiled Lisp files, are not stored in Bazaar. Therefore, to +build from Bazaar you must run "make bootstrap" instead of just "make": + + $ cvs update -dP + $ make bootstrap + +Normally, it is not necessary to use "make bootstrap" after every +update from Bazaar. "make" should work in 90% of the cases and be +much quicker. + + $ make + +(If you want to install the Emacs binary, type "make install" instead +of "make" in the last command.) + +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 +updated to reflect new autoloaded functions. If you see errors (rather +than warnings) about undefined lisp functions during compilation, that +may be the reason. Another symptom may be an error saying that +"loaddefs.el" could not be found; this is due to a change in the way +loaddefs.el was handled in version control, and should only happen +once, for users that are updating old sources. Finally, sometimes +there can be build failures related to *loaddefs.el (e.g. "required +feature `esh-groups' was not provided"). In that case, follow the +instructions below. + +To update loaddefs.el (and similar files), do: + + $ cd lisp + $ make autoloads + +If either of the above partial procedures fails, try "make bootstrap". +If CPU time is not an issue, the most thorough way to rebuild, and +avoid any spurious problems, is always to use this method. + +Users of non-Posix systems (MS-Windows etc.) should run the +platform-specific configuration scripts (nt/configure.bat, config.bat, +etc.) before "make bootstrap" or "make"; the rest of the procedure is +applicable to those systems as well. + +Questions, requests, and bug reports about the Bazaar versions of Emacs +should be sent to emacs-pretest-bug@gnu.org rather than gnu.emacs.help +or gnu.emacs.bug. Ideally, use M-x report-emacs-bug RET which will +send it to the proper place. + +Because the Bazaar version of Emacs is a work in progress, it will +sometimes fail to build. Please wait a day or so (and check the bug +and development mailing list archives) before reporting such problems. +In most cases, the problem is known about and is just waiting for +someone to fix it. + + +Note on accessing the Bazaar repository +--------------------------------------- + +Write access to the Bazaar repository is currently done via Bazaar's +sftp:// protocol; see http://www.emacswiki.org/emacs/BzrForEmacsDevs. +We plan to offer bzr+ssh:// access later. More discussion about that +is at https://savannah.gnu.org/support/?107077. + + + +This file is part of GNU Emacs. + +GNU Emacs is free software: you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation, either version 3 of the License, or +(at your option) any later version. + +GNU Emacs is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.