Mercurial > emacs
view INSTALL-CVS @ 51204:082b768216a0
Make (several) trivial substitutions for renamed and
new macros in dispextern.h, frame.h and window.h.
(x_draw_glyph_string_box): Adapt to per-window fringes and
scroll-bars.
(glyph_rect): Use window coordinates returned from
window_from_coordinates rather than frame_to_window_pixel_xy.
(XTset_vertical_scroll_bar): Adapt to per-window fringes and
scroll-bars.
(w32_clip_to_row): Remove superfluous whole_line_p arg and code
(fringes are now inside margins, i.e. always in the clipping area).
All callers changed.
(x_new_font): Set FRAME_COLUMN_WIDTH and FRAME_LINE_HEIGHT
directly, then call compute_fringe_widths. Don't call
frame_update_line_height.
author | Kim F. Storm <storm@cua.dk> |
---|---|
date | Sat, 24 May 2003 22:06:19 +0000 |
parents | ca7aa82d6f39 |
children | 88cd9cfe5459 |
line wrap: on
line source
Building and Installing Emacs from CVS Some of the files that are included in the Emacs tarball, such as byte-compiled Lisp files, are not stored in the CVS repository. Therefore, to build from CVS you must run "make bootstrap" instead of just "make": $ ./configure $ make bootstrap The bootstrap process makes sure all necessary files are rebuilt before it builds the final Emacs binary. Normally, it is not necessary to use "make bootstrap" after every CVS update. Unless there are problems, we suggest the following procedure: $ ./configure $ make $ cd lisp $ make recompile EMACS=../src/emacs $ cd .. $ make (If you want to install the Emacs binary, type "make install" instead of "make" in the last command.) If the above procedure fails, try "make bootstrap". 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. Note that "make bootstrap" overwrites some files that are under CVS control, such as lisp/loaddefs.el. This could produce CVS conflicts next time that you resync with the CVS. If you see such conflicts, overwrite your local copy of the file with the clean version from the CVS repository. For example: cvs update -C lisp/loaddefs.el Questions, requests, and bug reports about the CVS versions of Emacs sould be sent to emacs-pretest-bug@gnu.org rather.