Mercurial > hg > xemacs-beta

comparison INSTALL @ 201:eb5470882647 r20-3b27

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-3b27
author cvs
date Mon, 13 Aug 2007 10:01:22 +0200
parents 3d6bfa290dbd
children d44af0c54775
comparison
equal deleted inserted replaced
200:f0deb0c0e6be 201:eb5470882647
56 If you want users on other systems to be able to use the XEmacs you 56 If you want users on other systems to be able to use the XEmacs you
57 have built, try to build those packages so that the generated 57 have built, try to build those packages so that the generated
58 libraries are statically linked. 58 libraries are statically linked.
59 59
60 Use the --site-includes and --site-libraries options when building 60 Use the --site-includes and --site-libraries options when building
61 XEmacs to allow configure to find the external software packages. 61 XEmacs to allow configure to find the external software packages.
62 If you link with dynamic (``.so'') external package libraries, which
63 is not recommended, you will also need to add the library directories
64 to the --site-runtime-libraries option.
62 65
63 66
64 3) In the top level directory of the XEmacs distribution, run the 67 3) In the top level directory of the XEmacs distribution, run the
65 program `configure' as follows: 68 program `configure' as follows:
66 69
92 files and object libraries. You may specify multiple DIR's by 95 files and object libraries. You may specify multiple DIR's by
93 enclosing the list in quotes. All the external packages you want to 96 enclosing the list in quotes. All the external packages you want to
94 use with XEmacs (e.g. xpm, wnn, ...) described later should have their 97 use with XEmacs (e.g. xpm, wnn, ...) described later should have their
95 include and library directories defined using these options. 98 include and library directories defined using these options.
96 99
97 The `--site-runtime-libraries=DIR' option specifies additional 100 The `--site-runtime-libraries=DIR' option specifies directories to
98 directories to search for shared libraries at run time. This may be 101 search for shared libraries at run time. This may be necessary if you
99 necessary on some systems, or if you expect some of the libraries used 102 link with dynamic libraries that are installed in non-standard
100 to build XEmacs to be in a different directory at run time than at 103 directories, or if you expect some of the libraries used to build
101 build time. Usually this will add a `-R' to each directory specified 104 XEmacs to be in a different directory at run time than at build time.
102 and use that when linking XEmacs. 105 Usually this will add a `-R' to each directory specified and use that
106 when linking XEmacs. If you use this option, you must specify ALL of
107 the directories containing shared libraries at run time, including
108 system directories.
109
110 Rationale: Some people think that directories in --site-libraries
111 should be automatically used to update --site-runtime-libraries.
112 Here's a real-life scenario that explains why this is not done: You
113 build binaries for your company using static libs in
114 /net/toy/hack/lib. XEmacs adds /net/toy/hack/lib to the runpath of
115 the executable you've built. Since there are only static libs there,
116 the system runtime loader will look in this dir, and ignore it,
117 causing only a .01 second delay in starting XEmacs. You leave the
118 company for a job at a small Silicon Valley startup. Time passes.
119 The next guy who inherits your machine objects to working on a machine
120 named `toy', and gets the sysadmin to rename the machine `godzilla'.
121 The SA forgets to remove the old entry for `toy' from the hosts file.
122 Now the system loader will still try to access /net/toy/, and the
123 automounter will hang trying to access /net/toy. XEmacs suddenly
124 takes 30 seconds longer to start up, no one can figure out why, and
125 everyone at your old company curses your name, thinking that you've
126 put a time bomb into XEmacs. And they're right!
103 127
104 The `--with-gcc' option specifies that the build process should 128 The `--with-gcc' option specifies that the build process should
105 compile XEmacs using GCC. The `--compiler' option allows you to 129 compile XEmacs using GCC. The `--compiler' option allows you to
106 specify some other compiler to be used to compile XEmacs. If neither 130 specify some other compiler to be used to compile XEmacs. If neither
107 option is specified, the environment variable CC is used instead. 131 option is specified, the environment variable CC is used instead.