Mercurial > emacs

comparison INSTALL @ 9507:6773cf9c2e75

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
entered into RCS
author Richard M. Stallman <rms@gnu.org>
date Thu, 13 Oct 1994 04:05:41 +0000
parents 151b595bc41a
children 05fbcd364e6e
comparison
equal deleted inserted replaced
9506:2341ee469132 9507:6773cf9c2e75
416 416
417 4) Create `Makefile' files in various other directories 417 4) Create `Makefile' files in various other directories
418 from the corresponding `Makefile.in' files. This isn't so hard, 418 from the corresponding `Makefile.in' files. This isn't so hard,
419 just a matter of substitution. 419 just a matter of substitution.
420 420
421 5) If you're going to use the build-install script to build Emacs,
422 copy `./build-ins.in' to `./build-install', and edit the
423 definitions found at the top of the script.
424
425 The `configure' script is built from `configure.in' by the `autoconf' 421 The `configure' script is built from `configure.in' by the `autoconf'
426 program. However, since Emacs has configuration requirements that 422 program. However, since Emacs has configuration requirements that
427 autoconf can't meet, `configure.in' uses an marriage of custom-baked 423 autoconf can't meet, `configure.in' uses an marriage of custom-baked
428 configuration code and autoconf macros. New versions of autoconf 424 configuration code and autoconf macros. New versions of autoconf
429 could very well break this arrangement, so it may be wise to avoid 425 could very well break this arrangement, so it may be wise to avoid
430 rebuilding `configure' from `configure.in' when possible. 426 rebuilding `configure' from `configure.in' when possible.
431 427
432 428
433 BUILDING GNU EMACS BY HAND 429 BUILDING GNU EMACS BY HAND
434 430
435 Once Emacs is configured, running `make' or running the shell script 431 Once Emacs is configured, running `make' in the top directory performs
436 `build-install' in the top directory performs the following steps. 432 the following steps.
437 433
438 1) Run `make src/paths.h' in the top directory. This produces 434 1) Run `make src/paths.h' in the top directory. This produces
439 `./src/paths.h' from the template file `./src/paths.h.in', changing 435 `./src/paths.h' from the template file `./src/paths.h.in', changing
440 the paths to the values specified in `./Makefile'. 436 the paths to the values specified in `./Makefile'.
441 437
459 version. 455 version.
460 456
461 457
462 INSTALLATION BY HAND 458 INSTALLATION BY HAND
463 459
464 The steps below are done by the shell script `build-install' or by 460 The steps below are done by running `make install' in the main
465 running `make install' in the main directory of the Emacs 461 directory of the Emacs distribution.
466 distribution.
467 462
468 1) Copy `./lisp' and its subdirectories, `./etc', and the executables 463 1) Copy `./lisp' and its subdirectories, `./etc', and the executables
469 in `./lib-src' to their final destinations, as selected in `./src/paths.h'. 464 in `./lib-src' to their final destinations, as selected in `./src/paths.h'.
470 465
471 Strictly speaking, not all of the executables in `./lib-src' need be copied. 466 Strictly speaking, not all of the executables in `./lib-src' need be copied.