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