Mercurial > vim
comparison src/INSTALLpc.txt @ 2951:57a7998e0fa8 v7.3.248
updated for version 7.3.248
Problem: PC Install instructions missing install instructions.
Solution: Step-by-step explanation. (Michael Soyka)
author | Bram Moolenaar <bram@vim.org> |
---|---|
date | Fri, 15 Jul 2011 13:52:04 +0200 |
parents | 82cd9f1e8d6b |
children | f2de38a019a2 |
comparison
equal
deleted
inserted
replaced
2950:aa84232e73d1 | 2951:57a7998e0fa8 |
---|---|
9 | 9 |
10 The file "feature.h" can be edited to match your preferences. You can skip | 10 The file "feature.h" can be edited to match your preferences. You can skip |
11 this, then you will get the default behavior as is documented, which should | 11 this, then you will get the default behavior as is documented, which should |
12 be fine for most people. | 12 be fine for most people. |
13 | 13 |
14 With the exception of the last two sections (Windows 3.1 and MS-DOS), | 14 With the exception of two sections (Windows 3.1 and MS-DOS), this document |
15 this document assumes that you are building Vim for Win32 | 15 assumes that you are building Vim for Win32 or later. |
16 (Windows NT/2000/XP/2003/Vista and Windows 95/98/Me) | 16 (Windows 95/98/Me/NT/2000/XP/2003/Vista/7) |
17 | 17 |
18 | 18 |
19 Contents: | 19 Contents: |
20 1. Microsoft Visual C++ | 20 1. Microsoft Visual C++ |
21 2. Using MinGW | 21 2. Using MinGW |
24 5. Cross compiling for Win32 from a Linux machine | 24 5. Cross compiling for Win32 from a Linux machine |
25 6. Building with Python support | 25 6. Building with Python support |
26 7. Building with MzScheme support | 26 7. Building with MzScheme support |
27 8. Windows 3.1 | 27 8. Windows 3.1 |
28 9. MS-DOS | 28 9. MS-DOS |
29 | |
30 10. Installing after building from sources | |
31 | |
29 | 32 |
30 The currently preferred method is using the free Visual C++ Toolkit 2008 | 33 The currently preferred method is using the free Visual C++ Toolkit 2008 |
31 |msvc-2008-express|, the produced binary runs on most MS-Windows systems. If | 34 |msvc-2008-express|, the produced binary runs on most MS-Windows systems. If |
32 you need the executable to run on Windows 98 or ME, use the 2003 one | 35 you need the executable to run on Windows 98 or ME, use the 2003 one |
33 |msvc-2003-toolkit|. | 36 |msvc-2003-toolkit|. |
407 NOTE: multi-byte support is broken in the Borland libraries, not everything | 410 NOTE: multi-byte support is broken in the Borland libraries, not everything |
408 will work properly! Esp. handling multi-byte file names. | 411 will work properly! Esp. handling multi-byte file names. |
409 | 412 |
410 If you get all kinds of strange error messages when compiling, try adding | 413 If you get all kinds of strange error messages when compiling, try adding |
411 changing the file format from "unix" to "dos". | 414 changing the file format from "unix" to "dos". |
415 | |
416 | |
417 10. Installing after building from sources | |
418 ========================================== | |
419 | |
420 [provided by Michael Soyka] | |
421 | |
422 After you've built the Vim binaries as described above, you're ready to | |
423 install Vim on your system. However, if you've obtained the Vim sources | |
424 using Mercurial or by downloading them as a unix tar file, you must first | |
425 create a "vim73" directory. If you instead downloaded the sources as | |
426 zip files, you can skip this setup as the zip archives already have the | |
427 correct directory structure. | |
428 | |
429 A. Create a Vim "runtime" subdirectory named "vim73" | |
430 ----------------------------------------------------- | |
431 If you obtained your Vim sources as zip files, you can skip this step. | |
432 Otherwise, continue reading. | |
433 | |
434 Go to the directory that contains the Vim "src" and "runtime" | |
435 directories and create a new subdirectory named "vim73". | |
436 | |
437 Copy the "runtime" files into "vim73": | |
438 copy runtime\* vim73 | |
439 | |
440 B. Copy the new binaries into the "vim73" directory | |
441 ---------------------------------------------------- | |
442 Regardless of how you installed the Vim sources, you need to copy the | |
443 new binaries you created above into "vim73": | |
444 | |
445 copy src\*.exe vim73 | |
446 copy src\GvimExt\gvimext.dll vim73 | |
447 copy src\xxd\xxd.exe vim73 | |
448 | |
449 C. Move the "vim73" directory into the Vim installation subdirectory | |
450 --------------------------------------------------------------------- | |
451 Move the "vim73" subdirectory into the subdirectory where you want Vim | |
452 to be installed. Typically, this subdirectory will be named "vim". | |
453 If you already have a "vim73" subdirectory in "vim", delete it first | |
454 by running its unstal.exe program. | |
455 | |
456 D. Install Vim | |
457 --------------- | |
458 "cd" to your Vim installation subdirectory "vim\vim73" and run the | |
459 "install.exe" program. It will ask you a number of questions about | |
460 how you would like to have your Vim setup. Among these are: | |
461 - You can tell it to write a "_vimrc" file with your preferences in the | |
462 parent directory. | |
463 - It can also install an "Edit with Vim" entry in the Windows Explorer | |
464 popup menu. | |
465 - You can have it create batch files, so that you can run Vim from the | |
466 console or in a shell. You can select one of the directories in your | |
467 PATH or add the directory to PATH using the Windows Control Panel. | |
468 - Create entries for Vim on the desktop and in the Start menu. | |
469 | |
470 Happy Vimming! |