Mercurial > vim
comparison src/INSTALL @ 7:3fc0f57ecb91 v7.0001
updated for version 7.0001
author | vimboss |
---|---|
date | Sun, 13 Jun 2004 20:20:40 +0000 |
parents | |
children | 4424b47a0797 |
comparison
equal
deleted
inserted
replaced
6:c2daee826b8f | 7:3fc0f57ecb91 |
---|---|
1 INSTALL - Installation of Vim on different machines. | |
2 | |
3 This file contains instructions for compiling Vim. If you already have an | |
4 executable version of Vim, you don't need this. | |
5 | |
6 Contents: | |
7 1. Generic | |
8 2. Unix | |
9 3. RISC OS | |
10 4. Macintosh | |
11 5. OS/2 (with EMX 0.9b) | |
12 6. Atari MiNT | |
13 | |
14 For OS/390 Unix see ../runtime/doc/os_390.txt | |
15 For BeBox see ../runtime/doc/os_beos.txt. | |
16 For Amiga see INSTALLami.txt | |
17 For PC (MS-DOS, Windows NT, Windows 95) see INSTALLpc.txt | |
18 For Macintosh see INSTALLmac.txt | |
19 | |
20 | |
21 1. Generic | |
22 ========== | |
23 | |
24 If you compile Vim without specifying anything, you will get the default | |
25 behaviour as is documented, which should be fine for most people. | |
26 | |
27 For features that you can't enable/disable in another way, you can edit the | |
28 file "feature.h" to match your preferences. | |
29 | |
30 | |
31 2. Unix | |
32 ======= | |
33 | |
34 Summary: | |
35 1. make run configure, compile and link | |
36 2. make install installation in /usr/local | |
37 | |
38 This will include the GUI and X11 libraries, if you have them. If you want a | |
39 version of Vim that is small and starts up quickly, see the Makefile for how | |
40 to disable the GUI and X11. If you don't have Motif and/or X11, these | |
41 features will be disabled automatically. | |
42 | |
43 See the start of Makefile for more detailed instructions about how to compile | |
44 Vim. | |
45 | |
46 If you need extra compiler and/or linker arguments, set $CFLAGS and/or $LIBS | |
47 before starting configure. Example: | |
48 | |
49 env CFLAGS=-I/usr/local/include LIBS=-lm make | |
50 | |
51 This is only needed for things that configure doesn't offer a specific argument | |
52 for or figures out by itself. First try running configure without extra | |
53 arguments. | |
54 | |
55 GNU Autoconf and a few other tools have been used to make Vim work on many | |
56 different Unix systems. The advantage of this is that Vim should compile | |
57 on most sytems without any adjustments. The disadvantage is that when | |
58 adjustments are required, it takes some time to understand what is happening. | |
59 | |
60 If configure finds all library files and then complains when linking that some | |
61 of them can't be found, your linker doesn't return an error code for missing | |
62 libraries. Vim should be linked fine anyway, mostly you can just ignore these | |
63 errors. | |
64 | |
65 If you run configure by hand (not using the Makefile), remember that any | |
66 changes in the Makefile have no influence on configure. This may be what you | |
67 want, but maybe not! | |
68 | |
69 The advantage of running configure separately, is that you can write a script | |
70 to build Vim, without changing the Makefile or feature.h. Example (using sh): | |
71 | |
72 CFLAGS=-DCOMPILER_FLAG ./configure --enable-gui=motif | |
73 | |
74 One thing to watch out for: If the configure script itself changes, running | |
75 "make" will execute it again, but without your arguments. Do "make clean" and | |
76 run configure again. | |
77 | |
78 If you are compiling Vim for several machines, for each machine: | |
79 a. make shadow | |
80 b. mv shadow machine_name | |
81 c. cd machine_name | |
82 d. make; make install | |
83 | |
84 [Don't use a path for machine_name, just a directory name, otherwise the links | |
85 that "make shadow" creates won't work.] | |
86 | |
87 | |
88 Unix: COMPILING WITH/WITHOUT GUI | |
89 | |
90 These configure arguments can be used to select which GUI to use: | |
91 --enable-gui= gtk, motif, athena or auto | |
92 --disable-gtk-check | |
93 --disable-motif-check | |
94 --disable-athena-check | |
95 | |
96 --enable-gui defaults to "auto", so it will automatically look for a GUI (in | |
97 the order of GTK, Motif, then Athena). If one is found, then is uses it and | |
98 does not proceed to check any of the remaining ones. Otherwise, it moves on | |
99 to the next one. | |
100 | |
101 --enable-{gtk,motif,athena}-check all default to "yes", such that if | |
102 --enable-gui is "auto" (which it is by default), GTK, Motif, and Athena will | |
103 be checked for. If you want to *exclude* a certain check, then you use | |
104 --disable-{gtk,motif,athena}-check. | |
105 | |
106 For example, if --enable-gui is set to "auto", but you don't want it look for | |
107 Motif, you then also specify --disable-motif-check. This results in only | |
108 checking for GTK and Athena. | |
109 | |
110 Lastly, if you know which one you want to use, then you can just do | |
111 --enable-gui={gtk,motif,athena}. So if you wanted to only use Motif, then | |
112 you'd specify --enable-gui=motif. Once you specify what you want, the | |
113 --enable-{gtk,motif,athena}-check options are ignored. | |
114 | |
115 For compiling with the GTK+ GUI, you need a recent version of glib and gtk+. | |
116 Configure checks for at least version 1.1.16, but below 2.0. An older versions | |
117 is not selected automatically. If you want to use it anyway, run configure | |
118 with "--disable-gtktest". GTK 2.0 doesn't work yet. | |
119 GTK requires an ANSI C compiler. If you fail to compile Vim with GTK+ (it | |
120 is the preferred choice), try selecting another one in the Makefile. | |
121 If you are sure you have GTK installed, but for some reason configure says you | |
122 do not, you may have left-over header files and/or library files from an older | |
123 (and incompatible) version of GTK. if this is the case, please check | |
124 auto/config.log for any error messages that may give you a hint as to what's | |
125 happening. | |
126 | |
127 Unix: COMPILING WITH MULTI-BYTE | |
128 | |
129 When you want to compile with the multi-byte features enabled, make sure you | |
130 compile on a machine where the locale settings actually work. otherwise the | |
131 configure tests may fail. You need to compile with "big" features: | |
132 | |
133 ./configure --with-features=big | |
134 | |
135 Unix: COMPILING ON LINUX | |
136 | |
137 On Linux, when using -g to compile (which is default for gcc), the executable | |
138 will probably be statically linked. If you don't want this, remove the -g | |
139 option from CFLAGS. | |
140 | |
141 Unix: PUTTING vimrc IN /etc | |
142 | |
143 Some Linux distributions prefer to put the global vimrc file in /etc, and the | |
144 Vim runtime files in /usr. This can be done with: | |
145 ./configure --prefix=/usr | |
146 make VIMRCLOC=/etc VIMRUNTIMEDIR=/usr/share/vim MAKE="make -e" | |
147 | |
148 Unix: COMPILING ON NeXT | |
149 | |
150 Add the "-posix" argument to the compiler by using one of these commands: | |
151 setenv CC 'cc -posix' (csh) | |
152 export CC='cc -posix' (sh) | |
153 And run configure with "--disable-motif-check". | |
154 | |
155 | |
156 3. RISC OS | |
157 ============= | |
158 | |
159 Much file renaming is needed before you can compile anything. | |
160 You'll need UnixLib to link against, GCC and GNU make. | |
161 | |
162 I suggest you get the RISC OS binary distribution, which includes the | |
163 Templates file and the loader. | |
164 | |
165 Try here: http://www.ecs.soton.ac.uk/~tal197 | |
166 | |
167 Do | |
168 :help riscos | |
169 | |
170 within the editor for more information, or read the os_riscos.txt help file. | |
171 | |
172 | |
173 4. Macintosh | |
174 ============ | |
175 | |
176 Vim should work on the Macintosh, but I don't have a makefile for it. | |
177 Work is being done to update the Macintosh port. It's a lot of work; don't | |
178 expect it soon. | |
179 | |
180 | |
181 5. OS/2 | |
182 ======= | |
183 | |
184 Summary: | |
185 ren Makefile Makefile.unix | |
186 ren makefile.os2 Makefile | |
187 make | |
188 | |
189 This port of Vim to OS/2 is based on the emx environment together | |
190 with GNU C. The main design goal of emx is to simplify porting Unix | |
191 software to OS/2 and DOS. Because of this, almost all the Unix defines | |
192 etc. already existing in the Vim source code could be reused. Only where | |
193 OS/2 specifics came into play were additional changes necessary. Those | |
194 places can be found by searching for "OS2" and "__EMX__" (I've tried to | |
195 keep emx-specific things separate from generic OS/2 stuff). | |
196 | |
197 Note: This OS/2 port works well for me and an additional OS/2 user on | |
198 the Vim development team (Karsten Sievert); however, since I | |
199 haven't had any other feedback from other people, that either | |
200 means no (OS/2-specific) bugs exist, or no one has yet created | |
201 a situation in which any bugs are apparent. | |
202 Report any problems or other comments to paul@wau.mis.ah.nl | |
203 (email valid up to at least September 1996, after that try | |
204 paul@wurtel.hobby.nl, paul@murphy.nl, or paulS@toecompst.nl). | |
205 Textmode/notextmode and binary mode both seem to work well. | |
206 | |
207 Prerequisites: | |
208 - To compile, you need the emx environment (at least rev. 0.9b), GCC, | |
209 some make utility (GNU make works fine). These are generally | |
210 available as (ask Archie about them): | |
211 emxrt.zip emx runtime package | |
212 emxdev.zip emx development system (without compiler) | |
213 GNU programs compiled for emx, patches and patched sources: | |
214 gnudev1.zip GNU development tools compiled for emx (part 1) | |
215 gnudev2.zip GNU development tools compiled for emx (part 2) | |
216 gnumake.zip GNU make | |
217 - Don't set a TERM environment variable; Vim defaults to os2ansi | |
218 which is available as a builtin termcap entry. Using other values | |
219 may give problems! (OS/2 ANSI emulation is quite limited.) If you | |
220 need to set TERM for other programs, you may consider putting | |
221 set term=os2ansi in the vimrc file. | |
222 | |
223 Check vim_os2.txt for additional info on running Vim. | |
224 | |
225 | |
226 6. Atari MiNT | |
227 ============= | |
228 | |
229 | |
230 To compile Vim for MiNT you may either copy makefile.mint to Makefile or use | |
231 the Unix Makefile adapted for the MiNT configuration. | |
232 | |
233 Now proceed as described in the Unix section. | |
234 | |
235 Prerequisites: | |
236 | |
237 You need a curses or termcap library that supports non-alphanumeric | |
238 termcap names. If you don't have any, link with termlib.o. | |
239 | |
240 ----------------------------------------------------------------------------- | |
241 | |
242 The rest of this file is based on the INSTALL file that comes with GNU | |
243 autoconf 2.12. Not everything applies to Vim. Read Makefile too! | |
244 | |
245 | |
246 Basic Installation | |
247 ================== | |
248 | |
249 These are generic installation instructions. | |
250 | |
251 The `configure' shell script attempts to guess correct values for | |
252 various system-dependent variables used during compilation. It uses | |
253 those values to create a `Makefile' in each directory of the package. | |
254 It may also create one or more `.h' files containing system-dependent | |
255 definitions. Finally, it creates a shell script `config.status' that | |
256 you can run in the future to recreate the current configuration, a file | |
257 `config.cache' that saves the results of its tests to speed up | |
258 reconfiguring, and a file `config.log' containing compiler output | |
259 (useful mainly for debugging `configure'). | |
260 | |
261 If you need to do unusual things to compile the package, please try | |
262 to figure out how `configure' could check whether to do them, and mail | |
263 diffs or instructions to the address given in the `README' so they can | |
264 be considered for the next release. If at some point `config.cache' | |
265 contains results you don't want to keep, you may remove or edit it. | |
266 | |
267 The file `configure.in' is used to create `configure' by a program | |
268 called `autoconf'. You only need `configure.in' if you want to change | |
269 it or regenerate `configure' using a newer version of `autoconf'. | |
270 | |
271 The simplest way to compile this package is: | |
272 | |
273 1. `cd' to the directory containing the package's source code and type | |
274 `./configure' to configure the package for your system. If you're | |
275 using `csh' on an old version of System V, you might need to type | |
276 `sh ./configure' instead to prevent `csh' from trying to execute | |
277 `configure' itself. | |
278 | |
279 Running `configure' takes awhile. While running, it prints some | |
280 messages telling which features it is checking for. | |
281 | |
282 2. Type `make' to compile the package. | |
283 | |
284 3. Optionally, type `make check' to run any self-tests that come with | |
285 the package. | |
286 | |
287 4. Type `make install' to install the programs and any data files and | |
288 documentation. | |
289 | |
290 5. You can remove the program binaries and object files from the | |
291 source code directory by typing `make clean'. To also remove the | |
292 files that `configure' created (so you can compile the package for | |
293 a different kind of computer), type `make distclean'. There is | |
294 also a `make maintainer-clean' target, but that is intended mainly | |
295 for the package's developers. If you use it, you may have to get | |
296 all sorts of other programs in order to regenerate files that came | |
297 with the distribution. | |
298 | |
299 Compilers and Options | |
300 ===================== | |
301 | |
302 Some systems require unusual options for compilation or linking that | |
303 the `configure' script does not know about. You can give `configure' | |
304 initial values for variables by setting them in the environment. Using | |
305 a Bourne-compatible shell, you can do that on the command line like | |
306 this: | |
307 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure | |
308 | |
309 Or on systems that have the `env' program, you can do it like this: | |
310 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure | |
311 | |
312 Compiling For Multiple Architectures | |
313 ==================================== | |
314 | |
315 You can compile the package for more than one kind of computer at the | |
316 same time, by placing the object files for each architecture in their | |
317 own directory. To do this, you must use a version of `make' that | |
318 supports the `VPATH' variable, such as GNU `make'. `cd' to the | |
319 directory where you want the object files and executables to go and run | |
320 the `configure' script. `configure' automatically checks for the | |
321 source code in the directory that `configure' is in and in `..'. | |
322 | |
323 If you have to use a `make' that does not supports the `VPATH' | |
324 variable, you have to compile the package for one architecture at a time | |
325 in the source code directory. After you have installed the package for | |
326 one architecture, use `make distclean' before reconfiguring for another | |
327 architecture. | |
328 | |
329 Installation Names | |
330 ================== | |
331 | |
332 By default, `make install' will install the package's files in | |
333 `/usr/local/bin', `/usr/local/man', etc. You can specify an | |
334 installation prefix other than `/usr/local' by giving `configure' the | |
335 option `--prefix=PATH'. | |
336 | |
337 You can specify separate installation prefixes for | |
338 architecture-specific files and architecture-independent files. If you | |
339 give `configure' the option `--exec-prefix=PATH', the package will use | |
340 PATH as the prefix for installing programs and libraries. | |
341 Documentation and other data files will still use the regular prefix. | |
342 | |
343 In addition, if you use an unusual directory layout you can give | |
344 options like `--bindir=PATH' to specify different values for particular | |
345 kinds of files. Run `configure --help' for a list of the directories | |
346 you can set and what kinds of files go in them. | |
347 | |
348 If the package supports it, you can cause programs to be installed | |
349 with an extra prefix or suffix on their names by giving `configure' the | |
350 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. | |
351 | |
352 Optional Features | |
353 ================= | |
354 | |
355 Some packages pay attention to `--enable-FEATURE' options to | |
356 `configure', where FEATURE indicates an optional part of the package. | |
357 They may also pay attention to `--with-PACKAGE' options, where PACKAGE | |
358 is something like `gnu-as' or `x' (for the X Window System). The | |
359 `README' should mention any `--enable-' and `--with-' options that the | |
360 package recognizes. | |
361 | |
362 For packages that use the X Window System, `configure' can usually | |
363 find the X include and library files automatically, but if it doesn't, | |
364 you can use the `configure' options `--x-includes=DIR' and | |
365 `--x-libraries=DIR' to specify their locations. | |
366 | |
367 Specifying the System Type | |
368 ========================== | |
369 | |
370 There may be some features `configure' can not figure out | |
371 automatically, but needs to determine by the type of host the package | |
372 will run on. Usually `configure' can figure that out, but if it prints | |
373 a message saying it can not guess the host type, give it the | |
374 `--host=TYPE' option. TYPE can either be a short name for the system | |
375 type, such as `sun4', or a canonical name with three fields: | |
376 CPU-COMPANY-SYSTEM | |
377 | |
378 See the file `config.sub' for the possible values of each field. If | |
379 `config.sub' isn't included in this package, then this package doesn't | |
380 need to know the host type. | |
381 | |
382 If you are building compiler tools for cross-compiling, you can also | |
383 use the `--target=TYPE' option to select the type of system they will | |
384 produce code for and the `--build=TYPE' option to select the type of | |
385 system on which you are compiling the package. | |
386 | |
387 Sharing Defaults | |
388 ================ | |
389 | |
390 If you want to set default values for `configure' scripts to share, | |
391 you can create a site shell script called `config.site' that gives | |
392 default values for variables like `CC', `cache_file', and `prefix'. | |
393 `configure' looks for `PREFIX/share/config.site' if it exists, then | |
394 `PREFIX/etc/config.site' if it exists. Or, you can set the | |
395 `CONFIG_SITE' environment variable to the location of the site script. | |
396 A warning: not all `configure' scripts look for a site script. | |
397 | |
398 Operation Controls | |
399 ================== | |
400 | |
401 `configure' recognizes the following options to control how it | |
402 operates. | |
403 | |
404 `--cache-file=FILE' | |
405 Use and save the results of the tests in FILE instead of | |
406 `./config.cache'. Set FILE to `/dev/null' to disable caching, for | |
407 debugging `configure'. | |
408 | |
409 `--help' | |
410 Print a summary of the options to `configure', and exit. | |
411 | |
412 `--quiet' | |
413 `--silent' | |
414 `-q' | |
415 Do not print messages saying which checks are being made. To | |
416 suppress all normal output, redirect it to `/dev/null' (any error | |
417 messages will still be shown). | |
418 | |
419 `--srcdir=DIR' | |
420 Look for the package's source code in directory DIR. Usually | |
421 `configure' can determine that directory automatically. | |
422 | |
423 `--version' | |
424 Print the version of Autoconf used to generate the `configure' | |
425 script, and exit. | |
426 | |
427 `configure' also accepts some other, not widely useful, options. |