Mercurial > hg
annotate mcabber/INSTALL @ 1429:99d95d4ea806
No need to explicitly reset auto-away for directed presence messages
author | Mikael Berthe <mikael@lilotux.net> |
---|---|
date | Wed, 20 Feb 2008 07:49:11 +0100 |
parents | fff7ee4cefab |
children | bec235cd28a8 |
rev | line source |
---|---|
232 | 1 This file contains the generic instructions; the short version is: |
2 $ ./configure | |
3 $ make | |
4 ... and if you want to install the software: | |
5 $ make install | |
6 (If you don't want to install it, the "mcabber" binary lies in | |
7 the src/ directory after the build procedure) | |
8 | |
9 MCabber needs ncurses and ncurses development packages to build correctly. | |
934
a09bf67d1dfb
Unicode support depends on having ncursesw
Mikael Berthe <mikael@lilotux.net>
parents:
232
diff
changeset
|
10 For UTF-8 terminal support, use ncursesw instead. |
1090
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
11 Note: On FreeBSD (and maybe other BSD systems as well), it is recommended |
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
12 that you install ncurses from ports before compiling mcabber. |
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
13 You should also export LDFLAGS='-L/usr/local/lib' before running |
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
14 mcabber's configure to ensure that mcabber uses the ncurses installed |
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
15 from ports. This is necessary as the version of ncurses included in |
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
16 the base system does not provide unicode support. |
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
17 |
232 | 18 If you want SSL support, you will need openssl lib & dev packages as well. |
1090
fff7ee4cefab
Update INSTALL file: add a note for FreeBSD users
Mikael Berthe <mikael@lilotux.net>
parents:
1061
diff
changeset
|
19 |
1061 | 20 If you want PGP support, install libgpgme (with dev package), |
21 version >= 1.0.0. | |
232 | 22 |
23 Please have a look at the README file before launching mcabber. | |
24 | |
25 Please send me a message (mcabber AT lilotux DOT net) if you have | |
26 questions, suggestions or even patches... | |
27 | |
28 Mikael | |
29 | |
30 | |
57 | 31 Installation Instructions |
32 ************************* | |
33 | |
34 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free | |
35 Software Foundation, Inc. | |
36 | |
37 This file is free documentation; the Free Software Foundation gives | |
38 unlimited permission to copy, distribute and modify it. | |
39 | |
40 Basic Installation | |
41 ================== | |
42 | |
43 These are generic installation instructions. | |
44 | |
45 The `configure' shell script attempts to guess correct values for | |
46 various system-dependent variables used during compilation. It uses | |
47 those values to create a `Makefile' in each directory of the package. | |
48 It may also create one or more `.h' files containing system-dependent | |
49 definitions. Finally, it creates a shell script `config.status' that | |
50 you can run in the future to recreate the current configuration, and a | |
51 file `config.log' containing compiler output (useful mainly for | |
52 debugging `configure'). | |
53 | |
54 It can also use an optional file (typically called `config.cache' | |
55 and enabled with `--cache-file=config.cache' or simply `-C') that saves | |
56 the results of its tests to speed up reconfiguring. (Caching is | |
57 disabled by default to prevent problems with accidental use of stale | |
58 cache files.) | |
59 | |
60 If you need to do unusual things to compile the package, please try | |
61 to figure out how `configure' could check whether to do them, and mail | |
62 diffs or instructions to the address given in the `README' so they can | |
63 be considered for the next release. If you are using the cache, and at | |
64 some point `config.cache' contains results you don't want to keep, you | |
65 may remove or edit it. | |
66 | |
67 The file `configure.ac' (or `configure.in') is used to create | |
68 `configure' by a program called `autoconf'. You only need | |
69 `configure.ac' if you want to change it or regenerate `configure' using | |
70 a newer version of `autoconf'. | |
71 | |
72 The simplest way to compile this package is: | |
73 | |
74 1. `cd' to the directory containing the package's source code and type | |
75 `./configure' to configure the package for your system. If you're | |
76 using `csh' on an old version of System V, you might need to type | |
77 `sh ./configure' instead to prevent `csh' from trying to execute | |
78 `configure' itself. | |
79 | |
80 Running `configure' takes awhile. While running, it prints some | |
81 messages telling which features it is checking for. | |
82 | |
83 2. Type `make' to compile the package. | |
84 | |
85 3. Optionally, type `make check' to run any self-tests that come with | |
86 the package. | |
87 | |
88 4. Type `make install' to install the programs and any data files and | |
89 documentation. | |
90 | |
91 5. You can remove the program binaries and object files from the | |
92 source code directory by typing `make clean'. To also remove the | |
93 files that `configure' created (so you can compile the package for | |
94 a different kind of computer), type `make distclean'. There is | |
95 also a `make maintainer-clean' target, but that is intended mainly | |
96 for the package's developers. If you use it, you may have to get | |
97 all sorts of other programs in order to regenerate files that came | |
98 with the distribution. | |
99 | |
100 Compilers and Options | |
101 ===================== | |
102 | |
103 Some systems require unusual options for compilation or linking that the | |
104 `configure' script does not know about. Run `./configure --help' for | |
105 details on some of the pertinent environment variables. | |
106 | |
107 You can give `configure' initial values for configuration parameters | |
108 by setting variables in the command line or in the environment. Here | |
109 is an example: | |
110 | |
111 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix | |
112 | |
113 *Note Defining Variables::, for more details. | |
114 | |
115 Compiling For Multiple Architectures | |
116 ==================================== | |
117 | |
118 You can compile the package for more than one kind of computer at the | |
119 same time, by placing the object files for each architecture in their | |
120 own directory. To do this, you must use a version of `make' that | |
121 supports the `VPATH' variable, such as GNU `make'. `cd' to the | |
122 directory where you want the object files and executables to go and run | |
123 the `configure' script. `configure' automatically checks for the | |
124 source code in the directory that `configure' is in and in `..'. | |
125 | |
126 If you have to use a `make' that does not support the `VPATH' | |
127 variable, you have to compile the package for one architecture at a | |
128 time in the source code directory. After you have installed the | |
129 package for one architecture, use `make distclean' before reconfiguring | |
130 for another architecture. | |
131 | |
132 Installation Names | |
133 ================== | |
134 | |
135 By default, `make install' will install the package's files in | |
136 `/usr/local/bin', `/usr/local/man', etc. You can specify an | |
137 installation prefix other than `/usr/local' by giving `configure' the | |
138 option `--prefix=PREFIX'. | |
139 | |
140 You can specify separate installation prefixes for | |
141 architecture-specific files and architecture-independent files. If you | |
142 give `configure' the option `--exec-prefix=PREFIX', the package will | |
143 use PREFIX as the prefix for installing programs and libraries. | |
144 Documentation and other data files will still use the regular prefix. | |
145 | |
146 In addition, if you use an unusual directory layout you can give | |
147 options like `--bindir=DIR' to specify different values for particular | |
148 kinds of files. Run `configure --help' for a list of the directories | |
149 you can set and what kinds of files go in them. | |
150 | |
151 If the package supports it, you can cause programs to be installed | |
152 with an extra prefix or suffix on their names by giving `configure' the | |
153 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. | |
154 | |
155 Optional Features | |
156 ================= | |
157 | |
158 Some packages pay attention to `--enable-FEATURE' options to | |
159 `configure', where FEATURE indicates an optional part of the package. | |
160 They may also pay attention to `--with-PACKAGE' options, where PACKAGE | |
161 is something like `gnu-as' or `x' (for the X Window System). The | |
162 `README' should mention any `--enable-' and `--with-' options that the | |
163 package recognizes. | |
164 | |
165 For packages that use the X Window System, `configure' can usually | |
166 find the X include and library files automatically, but if it doesn't, | |
167 you can use the `configure' options `--x-includes=DIR' and | |
168 `--x-libraries=DIR' to specify their locations. | |
169 | |
170 Specifying the System Type | |
171 ========================== | |
172 | |
173 There may be some features `configure' cannot figure out automatically, | |
174 but needs to determine by the type of machine the package will run on. | |
175 Usually, assuming the package is built to be run on the _same_ | |
176 architectures, `configure' can figure that out, but if it prints a | |
177 message saying it cannot guess the machine type, give it the | |
178 `--build=TYPE' option. TYPE can either be a short name for the system | |
179 type, such as `sun4', or a canonical name which has the form: | |
180 | |
181 CPU-COMPANY-SYSTEM | |
182 | |
183 where SYSTEM can have one of these forms: | |
184 | |
185 OS KERNEL-OS | |
186 | |
187 See the file `config.sub' for the possible values of each field. If | |
188 `config.sub' isn't included in this package, then this package doesn't | |
189 need to know the machine type. | |
190 | |
191 If you are _building_ compiler tools for cross-compiling, you should | |
192 use the `--target=TYPE' option to select the type of system they will | |
193 produce code for. | |
194 | |
195 If you want to _use_ a cross compiler, that generates code for a | |
196 platform different from the build platform, you should specify the | |
197 "host" platform (i.e., that on which the generated programs will | |
198 eventually be run) with `--host=TYPE'. | |
199 | |
200 Sharing Defaults | |
201 ================ | |
202 | |
203 If you want to set default values for `configure' scripts to share, you | |
204 can create a site shell script called `config.site' that gives default | |
205 values for variables like `CC', `cache_file', and `prefix'. | |
206 `configure' looks for `PREFIX/share/config.site' if it exists, then | |
207 `PREFIX/etc/config.site' if it exists. Or, you can set the | |
208 `CONFIG_SITE' environment variable to the location of the site script. | |
209 A warning: not all `configure' scripts look for a site script. | |
210 | |
211 Defining Variables | |
212 ================== | |
213 | |
214 Variables not defined in a site shell script can be set in the | |
215 environment passed to `configure'. However, some packages may run | |
216 configure again during the build, and the customized values of these | |
217 variables may be lost. In order to avoid this problem, you should set | |
218 them in the `configure' command line, using `VAR=value'. For example: | |
219 | |
220 ./configure CC=/usr/local2/bin/gcc | |
221 | |
222 causes the specified `gcc' to be used as the C compiler (unless it is | |
223 overridden in the site shell script). Here is a another example: | |
224 | |
225 /bin/bash ./configure CONFIG_SHELL=/bin/bash | |
226 | |
227 Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent | |
228 configuration-related scripts to be executed by `/bin/bash'. | |
229 | |
230 `configure' Invocation | |
231 ====================== | |
232 | |
233 `configure' recognizes the following options to control how it operates. | |
234 | |
235 `--help' | |
236 `-h' | |
237 Print a summary of the options to `configure', and exit. | |
238 | |
239 `--version' | |
240 `-V' | |
241 Print the version of Autoconf used to generate the `configure' | |
242 script, and exit. | |
243 | |
244 `--cache-file=FILE' | |
245 Enable the cache: use and save the results of the tests in FILE, | |
246 traditionally `config.cache'. FILE defaults to `/dev/null' to | |
247 disable caching. | |
248 | |
249 `--config-cache' | |
250 `-C' | |
251 Alias for `--cache-file=config.cache'. | |
252 | |
253 `--quiet' | |
254 `--silent' | |
255 `-q' | |
256 Do not print messages saying which checks are being made. To | |
257 suppress all normal output, redirect it to `/dev/null' (any error | |
258 messages will still be shown). | |
259 | |
260 `--srcdir=DIR' | |
261 Look for the package's source code in directory DIR. Usually | |
262 `configure' can determine that directory automatically. | |
263 | |
264 `configure' also accepts some other, not widely useful, options. Run | |
265 `configure --help' for more details. | |
266 |