Source

build / build.texi

Diff from to

build.texi

 @c %**start of header
 @setfilename build.info
 @settitle XEmacs Build Reference Manual
+@dircategory Emacs
 @direntry
 * Build: (build).      Build XEmacs from within (UNIX, Windows).
 @end direntry
 * Build Overview::                    Overview of build package
 * Build Installation::                Installation of the build package
 * Build XEmacs::                      Choosing source and tools          
-* Build XEmacs From CVS::             Fetching sources with @code{CVS}
-* Build XEmacs From Tarballs::        Fetching source tarballs with @code{EFS}
+* Build XEmacs From CVS::             Fetching sources with CVS
+* Build XEmacs From Tarballs::        Fetching source tarballs with EFS
 * Build XEmacs With GNU Tools::       UNIX-style build using configure, make
 * Build XEmacs With Microsoft Tools:: Microsoft build using MS VC++ >= 4.0
 * Generate XEmacs Build Report::      Reporting Success or Failure
 @chapter Build Overview
 @cindex What build is
 
-@code{build} supports the building process of the @code{XEmacs} editor
-from its sources.
+@code{build} supports the building process of the XEmacs editor from its
+sources.
 
 @cindex XEmacs build process
 
 Run XEmacs command
 
 @example
-@kbd{M-x package-admin-add-binary-package RET @var{build-package-tarball-path}}
+@kbd{M-x package-admin-add-binary-package @key{RET} @var{build-package-tarball-path} @key{RET}}
 @end example
 
 after tarball download with EFS or ftp.
 Extract the build tarball(s) into the xemacs-packages hierarchy from
 your favorite shell.
 
-@code{bash}, @code{csh}, @code{ksh}, @code{zsh} come to mind on
-@code{UNIX} systems; @code{Cygwin's} @code{bash}, @code{cmd.exe}, and
-@code{command.exe} for @code{Windows 95/98/NT/2000}.
+@code{bash}, @code{csh}, @code{ksh}, @code{zsh} come to mind on UNIX
+systems; Cygwin's @code{bash}, @code{cmd.exe}, and @code{command.exe}
+for Windows 95/98/NT/2000.
 
 @example
 @kbd{cd @var{installation-directory}/xemacs-packages;
 @cindex Obtaining sources with CVS
 
 The CVS commands to fetch XEmacs source code are run through the XEmacs
-@kbd{compile} command (@pxref{Compilation, , , xemacs}).
+@code{compile} command (@pxref{Compilation, , , xemacs}).
 
 The buffers are named uniquely with the current working directory
 appropriately set to save the buffers with @kbd{C-x C-w} (@kbd{M-x
 [Download Build Tarball Set]
 @end example
 
-to fetch tarballs with @code{EFS}, which needs to be installed
-@footnote{If @code{EFS} is not installed you may obtain these tarballs
-by other means and extract them to the configured directory.}, followed
-by
+to fetch tarballs with EFS, which needs to be installed @footnote{If EFS
+is not installed you may obtain these tarballs by other means and
+extract them to the configured directory.}, followed by
 
 @example
 [Install Downloaded Build Tarball Set]
 @cindex make
 @cindex gcc
 
-Besides @code{GNU make} (make) and @code{GNU cc} (gcc) XEmacs can be built with the
-equivalent programs from many UNIX vendors.
+Besides GNU make (@code{make}) and GNU cc (@code{gcc}) XEmacs can be
+built with the equivalent programs from many UNIX vendors.
 
 The @dfn{configure}@footnote{This shell script is on the top-level of
 the XEmacs source tree, see also configure.usage there.} script, which