INSTALL.BZR 3.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. Copyright (C) 2002-2012 Free Software Foundation, Inc.
  2. See the end of the file for license conditions.
  3. Building and Installing Emacs from Bazaar
  4. Building Emacs from Bazaar requires some tools that are not needed
  5. when building from a release. You will need:
  6. autoconf - at least the version specified near the start of
  7. configure.in (in the AC_PREREQ command).
  8. automake - we recommend at least version 1.11.
  9. makeinfo - not strictly necessary, but highly recommended, so that
  10. you can build the manuals.
  11. The `autogen.sh' script can help you figure out if you have the
  12. necessary tools.
  13. The first time you build, there are a couple of extra steps.
  14. First, generate the `configure' script and some related files:
  15. $ ./autogen.sh
  16. (or you can just run `autoreconf -i -I m4').
  17. You can then configure your build (use `./configure --help' to see
  18. options you can set):
  19. $ ./configure
  20. If you want later builds to go faster, at the expense of sometimes
  21. doing the wrong thing if you update the build procedure, you can
  22. invoke "./configure -C --disable-maintainer-mode" instead.
  23. Some of the files that are included in the Emacs tarball, such as
  24. byte-compiled Lisp files, are not stored in Bazaar. Therefore, to
  25. build from Bazaar you must run "make bootstrap" instead of just "make":
  26. $ bzr pull
  27. $ make bootstrap
  28. Normally, it is not necessary to use "make bootstrap" after every
  29. update from Bazaar. "make" should work in 90% of the cases and be
  30. much quicker.
  31. $ make
  32. (If you want to install the Emacs binary, type "make install" instead
  33. of "make" in the last command.)
  34. Occasionally the file "lisp/loaddefs.el" (and similar automatically
  35. generated files, such as esh-groups.el, and *-loaddefs.el in some
  36. subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be
  37. updated to reflect new autoloaded functions. If you see errors (rather
  38. than warnings) about undefined lisp functions during compilation, that
  39. may be the reason. Finally, sometimes there can be build failures
  40. related to *loaddefs.el (e.g. "required feature `esh-groups' was not
  41. provided"). In that case, follow the instructions below.
  42. To update loaddefs.el (and similar files), do:
  43. $ cd lisp
  44. $ make autoloads
  45. If either of the above partial procedures fails, try "make bootstrap".
  46. If CPU time is not an issue, the most thorough way to rebuild, and
  47. avoid any spurious problems, is always to use this method.
  48. Users of non-Posix systems (MS-Windows etc.) should run the
  49. platform-specific configuration scripts (nt/configure.bat, config.bat,
  50. etc.) before "make bootstrap" or "make"; the rest of the procedure is
  51. applicable to those systems as well.
  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
  54. archives of the emacs-buildstatus, emacs-devel, and bug-gnu-emacs
  55. mailing lists) before reporting such problems. In most cases, the
  56. problem is known about and is just waiting for someone to fix it.
  57. This is especially true for Lisp compilation errors, which are almost
  58. never platform-specific.
  59. This file is part of GNU Emacs.
  60. GNU Emacs is free software: you can redistribute it and/or modify
  61. it under the terms of the GNU General Public License as published by
  62. the Free Software Foundation, either version 3 of the License, or
  63. (at your option) any later version.
  64. GNU Emacs is distributed in the hope that it will be useful,
  65. but WITHOUT ANY WARRANTY; without even the implied warranty of
  66. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  67. GNU General Public License for more details.
  68. You should have received a copy of the GNU General Public License
  69. along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.