Mercurial > vim
annotate src/INSTALLpc.txt @ 6999:dc1b678f0e4e v7.4.817
patch 7.4.817
Problem: Invalid memory access in file_pat_to_reg_pat().
Solution: Use vim_isspace() instead of checking for a space only. (Dominique
Pelle)
| author | Bram Moolenaar <bram@vim.org> |
|---|---|
| date | Tue, 11 Aug 2015 16:20:05 +0200 |
| parents | 112c80234ce3 |
| children | 2c5e813e8852 |
| rev | line source |
|---|---|
| 7 | 1 INSTALLpc.txt - Installation of Vim on PC |
| 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 | |
| 714 | 6 More information can be found here: (Very stale now.) |
| 7 | 7 |
| 714 | 8 http://mywebpage.netscape.com/sharppeople/vim/howto/ |
| 7 | 9 |
| 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 | |
| 12 be fine for most people. | |
| 13 | |
| 2951 | 14 With the exception of two sections (Windows 3.1 and MS-DOS), this document |
| 15 assumes that you are building Vim for Win32 or later. | |
| 16 (Windows 95/98/Me/NT/2000/XP/2003/Vista/7) | |
| 714 | 17 |
| 7 | 18 |
| 19 Contents: | |
| 714 | 20 1. Microsoft Visual C++ |
| 21 2. Using MinGW | |
| 22 3. Cygwin | |
| 23 4. Borland | |
| 24 5. Cross compiling for Win32 from a Linux machine | |
| 25 6. Building with Python support | |
| 26 7. Building with MzScheme support | |
| 27 8. Windows 3.1 | |
| 28 9. MS-DOS | |
| 29 | |
| 2951 | 30 10. Installing after building from sources |
| 31 | |
| 32 | |
| 1668 | 33 The currently preferred method is using the free Visual C++ Toolkit 2008 |
| 2871 | 34 |msvc-2008-express|, the produced binary runs on most MS-Windows systems. If |
| 35 you need the executable to run on Windows 98 or ME, use the 2003 one | |
| 36 |msvc-2003-toolkit|. | |
| 714 | 37 |
| 38 | |
| 39 1. Microsoft Visual C++ | |
| 40 ======================= | |
| 41 | |
| 42 Visual Studio | |
| 43 ------------- | |
| 44 | |
| 1608 | 45 Building with Visual Studio (VS 98, VS .NET, VS .NET 2003, VS 2005, and VS 2008) |
| 714 | 46 is straightforward. (These instructions should also work for VS 4 and VS 5.) |
| 47 | |
| 3847 | 48 Using VS C++ 2008 Express is recommended, the binaries build with that run on |
| 49 nearly all platforms. Binaries from later versions may not run on Windows 95 | |
| 50 or XP. | |
| 51 | |
| 714 | 52 To build Vim from the command line with MSVC, use Make_mvc.mak. |
| 53 Visual Studio installed a batch file called vcvars32.bat, which you must | |
| 54 run to set up paths for nmake and MSVC. | |
| 55 | |
| 856 | 56 nmake -f Make_mvc.mak console Win32 SDK or Microsoft Visual C++ |
| 57 nmake -f Make_mvc.mak GUI=yes GUI Microsoft Visual C++ | |
| 58 nmake -f Make_mvc.mak OLE=yes OLE Microsoft Visual C++ | |
| 714 | 59 nmake -f Make_mvc.mak PERL=C:\Perl PYTHON=C:\Python etc. |
| 856 | 60 Perl, Python, etc. |
| 714 | 61 |
| 62 Make_mvc.mak allows a Vim to be built with various different features and | |
| 63 debug support. Debugging with MS Devstudio is provided by Make_dvc.mak. | |
| 64 For a description of the use of Make_dvc.mak, look in Make_mvc.mak. | |
| 65 | |
| 66 For compiling Gvim with IME support on far-east Windows, add IME=yes | |
| 67 to the parameters you pass to Make_mvc.mak. | |
| 68 | |
| 69 To build Vim from within the Visual Studio IDE, open the Make_ivc.mak project. | |
| 70 (Note: Make_ivc.mak is not as rich as Make_mvc.mak, which allows for | |
| 71 far more configuration.) Make_ivc.mak can also be built with nmake. | |
| 72 | |
| 73 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim" | |
| 856 | 74 GUI Microsoft Visual C++ 4.x or later |
| 714 | 75 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim OLE" |
| 856 | 76 OLE Microsoft Visual C++ 4.x or later |
| 714 | 77 |
| 78 See the specific files for comments and options. | |
| 79 | |
| 80 These files have been supplied by George V. Reilly, Ben Singer, Ken Scott and | |
| 81 Ron Aaron; they have been tested. | |
| 82 | |
| 83 | |
| 1668 | 84 Visual C++ Toolkit 2003 *msvc-2003-toolkit* |
| 714 | 85 ----------------------- |
| 86 | |
| 1668 | 87 You could download the Microsoft Visual C++ Toolkit 2003 from |
| 714 | 88 http://msdn.microsoft.com/visualc/vctoolkit2003/ |
| 1668 | 89 Unfortunately this URL is no longer valid. Inofficial downloads appear to be |
| 90 available from links mentioned on these pages (use at your own risk): | |
| 91 http://www.filewatcher.com/m/VCToolkitSetup.exe.32952488.0.0.html | |
| 92 http://feargame.net/wiki/index.php?title=Building_Source_with_the_VC2003_Toolkit | |
| 93 | |
| 714 | 94 This contains the command-line tools (compiler, linker, CRT headers, |
| 95 and libraries) for Visual Studio .NET 2003, but not the Visual Studio IDE. | |
| 96 To compile and debug Vim with the VC2003 Toolkit, you will also need | |
| 97 |ms-platform-sdk|, |dotnet-1.1-redist|, |dotnet-1.1-sdk|, | |
| 98 and |windbg-download|. | |
| 99 | |
| 1569 | 100 It's easier to download Visual C++ 2008 Express Edition, |msvc-2008-express|, |
| 101 which is freely available in perpetuity. | |
| 714 | 102 |
| 103 The free Code::Blocks IDE works with the VC2003 Toolkit, as described at | |
| 104 http://wiki.codeblocks.org/index.php?title=Integrating_Microsoft_Visual_Toolkit_2003_with_Code::Blocks_IDE | |
| 105 (This site also takes you through configuring a number of other | |
| 106 free C compilers for Win32.) | |
| 107 | |
| 108 To compile Vim using the VC2003 Toolkit and Make_mvc.mak, you must first | |
| 109 execute the following commands in a cmd.exe window (the msvcsetup.bat batch | |
| 110 file can be used): | |
| 856 | 111 |
| 714 | 112 set PATH=%SystemRoot%\Microsoft.NET\Framework\v1.1.4322;%PATH% |
| 113 call "%VCToolkitInstallDir%vcvars32.bat" | |
| 114 set MSVCVer=7.1 | |
| 115 call "%ProgramFiles%\Microsoft Platform SDK\SetEnv.Cmd" | |
| 116 set LIB=%ProgramFiles%\Microsoft Visual Studio .NET 2003\Vc7\lib;%LIB% | |
| 117 | |
| 118 Now you can build Vim with Make_mvc.mak. | |
| 119 | |
| 120 | |
| 856 | 121 Getting the Windows Platform SDK *ms-platform-sdk* |
| 714 | 122 |
| 123 You will also need a copy of the Windows Platform SDK from | |
| 124 http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ | |
| 125 Specifically, you need the Windows Core SDK subset of the Platform SDK, | |
| 126 which contains the Windows headers and libraries. | |
| 127 | |
| 128 | |
| 129 Getting the .NET Framework 1.1 Runtime *dotnet-1.1-redist* | |
| 130 | |
| 131 You need the .NET Framework 1.1 Redistributable Package from | |
| 132 http://www.microsoft.com/downloads/details.aspx?familyid=262d25e3-f589-4842-8157-034d1e7cf3a3 | |
| 133 or from Windows Update: | |
| 134 http://windowsupdate.microsoft.com/ | |
| 135 This is needed to install |dotnet-1.1-sdk|. It also contains cvtres.exe, | |
| 136 which is needed to link Vim. | |
| 137 | |
| 138 | |
| 856 | 139 Getting the .NET Framework 1.1 SDK *dotnet-1.1-sdk* |
| 714 | 140 |
| 141 You need the .NET Framework 1.1 SDK from | |
| 142 http://www.microsoft.com/downloads/details.aspx?familyid=9b3a2ca6-3647-4070-9f41-a333c6b9181d | |
| 143 This contains some additional libraries needed to compile Vim, | |
| 144 such as msvcrt.lib. You must install |dotnet-1.1-redist| before | |
| 145 installing the .NET 1.1 SDK. | |
| 146 | |
| 147 | |
| 856 | 148 Getting the WinDbg debugger *windbg-download* |
| 714 | 149 |
| 150 The Debugging Tools for Windows can be downloaded from | |
| 151 http://www.microsoft.com/whdc/devtools/debugging/default.mspx | |
| 152 This includes the WinDbg debugger, which you will want if you ever need | |
| 153 to debug Vim itself. An earlier version of the Debugging Tools | |
| 154 is also available through the Platform SDK, |ms-platform-sdk|. | |
| 155 | |
| 156 | |
| 1608 | 157 Visual C++ 2005 Express Edition *msvc-2005-express* |
| 714 | 158 ------------------------------- |
| 159 | |
| 838 | 160 Visual C++ 2005 Express Edition can be downloaded for free from: |
| 714 | 161 http://msdn.microsoft.com/vstudio/express/visualC/default.aspx |
| 162 This includes the IDE and the debugger. You will also need | |
| 163 |ms-platform-sdk|. You can build Vim with Make_mvc.mak. | |
| 164 | |
| 165 Instructions for integrating the Platform SDK into VC Express: | |
| 166 http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/default.aspx | |
| 7 | 167 |
| 168 | |
| 1569 | 169 Visual C++ 2008 Express Edition *msvc-2008-express* |
| 170 ------------------------------- | |
| 171 | |
| 172 Visual C++ 2008 Express Edition can be downloaded for free from: | |
|
2217
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
173 http://www.microsoft.com/express/downloads/ |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
174 This includes the IDE and the debugger. |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
175 |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
176 To set the environment execute the msvc2008.bat script. You can then build |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
177 Vim with Make_mvc.mak. |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
178 |
| 3847 | 179 For building 64 bit binaries you also need to install the SDK: |
| 180 "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1" | |
| 181 You don't need the examples and documentation. | |
| 182 | |
|
2217
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
183 |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
184 Visual C++ 2010 Express Edition *msvc-2010-express* |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
185 ------------------------------- |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
186 |
|
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2098
diff
changeset
|
187 Visual C++ 2010 Express Edition can be downloaded for free from: |
| 1619 | 188 http://www.microsoft.com/express/vc/Default.aspx |
| 189 This includes the IDE and the debugger. | |
| 1569 | 190 |
| 2871 | 191 To set the environment execute the msvc2010.bat script. You can then build |
| 1619 | 192 Vim with Make_mvc.mak. |
| 1608 | 193 |
| 194 | |
| 6149 | 195 Targeting Windows XP with new MSVC *new-msvc-windows-xp* |
| 196 ---------------------------------- | |
| 197 | |
| 198 Beginning with Visual C++ 2010, Microsoft changed the behavior of LINK.EXE | |
| 199 so that it targets Windows 6.0 (Vista) by default. In order to override | |
| 200 this, the target Windows version number needs to be passed to LINK like | |
| 201 follows: | |
| 202 LINK ... /subsystem:console,5.01 | |
| 203 | |
| 204 Make_mvc.mak now supports a macro SUBSYSTEM_VER to pass the Windows version. | |
| 205 Use lines like follows to target Windows XP (assuming using Visual C++ 2012 | |
| 206 under 64-bit Windows): | |
| 207 set WinSdk71=%ProgramFiles(x86)%\Microsoft SDKs\Windows\v7.1A | |
| 208 set SDK_INCLUDE_DIR=%WinSdk71%\Include | |
| 209 set INCLUDE=%WinSdk71%\Include;%INCLUDE% | |
| 210 set LIB=%WinSdk71%\Lib;%LIB% | |
| 211 set PATH=%WinSdk71%\Bin;%PATH% | |
| 212 set CL=/D_USING_V110_SDK71_ | |
| 213 nmake -f Make_mvc.mak ... WINVER=0x0501 SUBSYSTEM_VER=5.01 | |
| 214 | |
| 215 The following Visual C++ team blog can serve as a reference page: | |
| 216 http://blogs.msdn.com/b/vcblog/archive/2012/10/08/windows-xp-targeting-with-c-in-visual-studio-2012.aspx | |
| 217 | |
| 218 | |
| 714 | 219 2. MinGW |
| 220 ======== | |
| 221 | |
| 222 (written by Ron Aaron: <ronaharon@yahoo.com>) | |
| 223 | |
| 224 This is about how to produce a Win32 binary of gvim with MinGW. | |
| 225 | |
| 226 First, you need to get the 'mingw32' compiler, which is free for the download | |
| 227 at: | |
| 228 | |
| 229 http://www.mingw.org/ | |
| 230 | |
| 6326 | 231 or you can use 'MinGW-w64' compiler. |
| 232 | |
| 233 http://mingw-w64.sourceforge.net/ | |
| 234 | |
| 714 | 235 Once you have downloaded the compiler binaries, unpack them on your hard disk |
| 236 somewhere, and put them on your PATH. If you are on Win95/98 you can edit | |
| 237 your AUTOEXEC.BAT file with a line like: | |
| 238 | |
| 6326 | 239 set PATH=C:\MinGW\bin;%PATH% |
| 714 | 240 |
| 241 or on NT/2000/XP, go to the Control Panel, (Performance and Maintenance), | |
| 242 System, Advanced, and edit the environment from there. | |
| 243 | |
| 244 Test if gcc is on your path. From a CMD (or COMMAND on '95/98) window: | |
| 245 | |
| 246 C:\> gcc --version | |
| 6326 | 247 gcc (GCC) 4.8.1 |
| 714 | 248 |
| 6326 | 249 C:\> mingw32-make --version |
| 250 GNU Make 3.82.90 (...etc...) | |
| 714 | 251 |
| 252 Now you are ready to rock 'n' roll. Unpack the vim sources (look on | |
| 253 www.vim.org for exactly which version of the vim files you need). | |
| 254 | |
| 255 Change directory to 'vim\src': | |
| 256 | |
| 257 C:\> cd vim\src | |
| 258 C:\VIM\SRC> | |
| 259 | |
| 260 and you type: | |
| 261 | |
| 6326 | 262 mingw32-make -f Make_ming.mak gvim.exe |
| 714 | 263 |
| 264 After churning for a while, you will end up with 'gvim.exe' in the 'vim\src' | |
| 265 directory. | |
| 266 | |
| 267 You should not need to do *any* editing of any files to get vim compiled this | |
| 268 way. If, for some reason, you want the console-mode-only version of vim (this | |
|
2098
3259c3923c1e
Updated runtime an documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
2088
diff
changeset
|
269 is NOT recommended on Win32, especially on '95/'98!!!), you can use: |
| 2035 | 270 |
| 6326 | 271 mingw32-make -f Make_ming.mak GUI=no vim.exe |
| 714 | 272 |
| 273 If you are dismayed by how big the EXE is, I strongly recommend you get 'UPX' | |
| 274 (also free!) and compress the file (typical compression is 50%). UPX can be | |
| 275 found at | |
| 276 http://www.upx.org/ | |
| 277 | |
| 3388 | 278 As of 2011, UPX still does not support compressing 64-bit EXE's; if you have |
| 279 built a 64-bit vim then an alternative to UPX is 'MPRESS'. MPRESS can be found | |
| 280 at: | |
| 281 http://www.matcode.com/mpress.htm | |
| 282 | |
| 283 | |
| 714 | 284 ADDITION: NLS support with MinGW |
| 285 | |
| 286 (by Eduardo F. Amatria <eferna1@platea.pntic.mec.es>) | |
| 287 | |
| 288 If you want National Language Support, read the file src/po/README_mingw.txt. | |
| 289 You need to uncomment lines in Make_ming.mak to have NLS defined. | |
| 290 | |
| 291 | |
| 292 3. Cygwin | |
| 293 ========= | |
| 294 | |
| 295 Use Make_cyg.mak with Cygwin's GCC. See | |
| 296 http://users.skynet.be/antoine.mechelynck/vim/compile.htm | |
| 297 | |
| 6326 | 298 With Cygnus gcc you should use the Unix Makefile instead (you need to get the |
| 714 | 299 Unix archive then). Then you get a Cygwin application (feels like Vim is |
|
2088
4ec11bb387a5
updated for version 7.2.372
Bram Moolenaar <bram@zimbu.org>
parents:
2035
diff
changeset
|
300 running on Unix), while with Make_cyg.mak you get a Windows application (like |
| 714 | 301 with the other makefiles). |
| 302 | |
| 303 | |
| 304 4. Borland | |
| 305 =========== | |
| 306 | |
| 307 Use Make_bc5.mak with Borland C++ 5.x. See | |
| 308 http://users.skynet.be/antoine.mechelynck/vim/compile.htm | |
| 309 | |
| 310 | |
| 311 5. Cross compiling for Win32 from a Linux machine | |
| 312 ================================================= | |
| 313 | |
| 314 [Update of 1) needs to be verified] | |
| 315 | |
| 316 If you like, you can compile the 'mingw' Win32 version from the comfort of | |
| 317 your Linux (or other unix) box. To do this, you need to follow a few steps: | |
| 318 1) Install the mingw32 cross-compiler. See | |
| 2035 | 319 http://www.mingw.org/wiki/LinuxCrossMinGW |
| 856 | 320 http://www.libsdl.org/extras/win32/cross/README.txt |
| 1619 | 321 2) Get and unpack both the Unix sources and the extra archive |
| 6326 | 322 3) in 'Make_cyg_ming.mak', set 'CROSS' to 'yes' instead of 'no'. |
| 323 Make further changes to 'Make_cyg_ming.mak' and 'Make_ming.mak' as you | |
| 324 wish. If your cross-compiler prefix differs from the predefined value, | |
| 2035 | 325 set 'CROSS_COMPILE' corresponding. |
| 714 | 326 4) make -f Make_ming.mak gvim.exe |
| 327 | |
| 328 Now you have created the Windows binary from your Linux box! Have fun... | |
| 329 | |
| 330 | |
| 331 6. Building with Python support | |
| 332 =============================== | |
| 333 | |
| 3847 | 334 For building with MSVC 2008 the "Windows Installer" from www.python.org |
| 335 works fine. | |
| 714 | 336 |
| 3847 | 337 (rest written by Ron Aaron: <ronaharon@yahoo.com>) |
| 338 | |
| 339 Building with the mingw32 compiler, and the ActiveState ActivePython: | |
| 714 | 340 http://www.ActiveState.com/Products/ActivePython/ |
| 341 | |
| 342 After installing the ActivePython, you will have to create a 'mingw32' | |
| 343 'libpython20.a' to link with: | |
| 344 cd $PYTHON/libs | |
| 345 pexports python20.dll > python20.def | |
| 346 dlltool -d python20.def -l libpython20.a | |
| 347 | |
| 348 Once that is done, edit the 'Make_ming.mak' so the PYTHON variable points to | |
| 349 the root of the Python installation (C:\Python20, for example). If you are | |
| 350 cross-compiling on Linux with the mingw32 setup, you need to also convert all | |
| 351 the 'Include' files to *unix* line-endings. This bash command will do it | |
| 352 easily: | |
| 353 for fil in *.h ; do vim -e -c 'set ff=unix|w|q' $fil | |
| 354 | |
| 355 Now just do: | |
| 356 make -f Make_ming.mak gvim.exe | |
| 357 | |
| 358 and you will end up with a Python-enabled, Win32 version. Enjoy! | |
| 359 | |
| 360 | |
| 361 7. Building with MzScheme support | |
| 362 ================================= | |
| 363 | |
| 364 (written by Sergey Khorev <sergey.khorev@gmail.com>) | |
| 365 | |
| 366 Vim with MzScheme (http://www.plt-scheme.org/software/mzscheme) support can | |
| 367 be built with either MSVC, or MinGW, or Cygwin. Supported versions are 205 and | |
| 368 above (including 299 and 30x series). | |
| 369 | |
| 370 The MSVC build is quite straightforward. Simply invoke (in one line) | |
| 371 nmake -fMake_mvc.mak MZSCHEME=<Path-to-MzScheme> | |
| 372 [MZSCHEME_VER=<MzScheme-version>] [DYNAMIC_MZSCHEME=<yes or no>] | |
| 373 where <MzScheme-version> is the last seven characters from MzScheme dll name | |
| 374 (libmzschXXXXXXX.dll). | |
| 375 If DYNAMIC_MZSCHEME=yes, resulting executable will not depend on MzScheme | |
| 376 DLL's, but will load them in runtime on demand. | |
| 377 | |
| 378 Building dynamic MzScheme support on MinGW and Cygwin is similar. Take into | |
| 379 account that <Path-to-MzScheme> should contain slashes rather than backslashes | |
| 380 (e.g. d:/Develop/MzScheme) | |
| 381 | |
| 382 "Static" MzScheme support (Vim executable will depend on MzScheme DLLs | |
| 383 explicitly) on MinGW and Cygwin requires additional step. | |
| 384 | |
| 385 libmzschXXXXXXX.dll and libmzgcXXXXXXX.dll should be copied from | |
| 386 %WINDOWS%\System32 to other location (either build directory, some temporary | |
| 387 dir or even MzScheme home). | |
| 388 | |
| 389 Pass that path as MZSCHEME_DLLS parameter for Make. E.g., | |
| 390 make -f Make_cyg.mak MZSCHEME=d:/Develop/MzScheme MZSCHEME_VER=209_000 | |
| 391 MZSCHEME_DLLS=c:/Temp DYNAMIC_MZSCHEME=no | |
| 392 | |
| 393 After a successful build, these dlls can be freely removed, leaving them in | |
| 394 %WINDOWS%\System32 only. | |
| 395 | |
| 396 | |
| 397 8. Windows 3.1x | |
| 398 =============== | |
| 399 | |
| 856 | 400 make -f Make_w16.mak 16 bit, Borland C++ 5.0 |
| 714 | 401 |
| 402 Warning: Be sure to use the right make.exe. It should be Borland make. | |
| 403 | |
| 404 You will almost certainly have to change the paths for libs and include files | |
| 405 in the Makefile. Look for "D:\BC5" and "ctl3dv2". You will get a number of | |
| 406 warnings which can be ignored ( _chmod, precompiled header files, and | |
| 407 "possibly incorrect assignment"). | |
| 408 | |
| 409 The makefile should also work for BC++ 4.0 and 4.5, but may need tweaking to | |
| 410 remove unsupported compiler & liker options. | |
| 411 | |
| 412 For making the Win32s version, you need Microsoft Visual C++ 4.1 OR EARLIER. | |
| 413 In MSVC 4.2 support for Win32s was dropped! Use this command: | |
| 414 nmake -f Make_mvc.mak GUI=yes | |
| 415 | |
| 416 | |
| 417 9. MS-DOS | |
| 7 | 418 ========= |
| 419 | |
| 420 Summary: | |
| 714 | 421 ren Make_bc3.mak Makefile; make 16 bit, Borland C++ and Turbo C++ |
| 422 ren Make_tcc.mak Makefile; make 16 bit, Turbo C | |
| 856 | 423 make -f Make_djg.mak 32 bit, DJGPP 2.0 |
| 424 make -f Make_bc5.mak 32 bit, Borland C++ 5.x (edit it to | |
| 425 define DOS) | |
| 7 | 426 |
| 427 Warning: Be sure to use the right make.exe. Microsoft C make doesn't work; | |
| 428 Borland make only works with Make_bc3.mak, Make_bc5.mak and Make_tcc.mak; | |
| 429 DJGPP/GNU make must be used for Make_djg.mak. | |
| 430 | |
| 431 The Borland C++ compiler has been used to generate the MS-DOS executable; it | |
| 432 should work without problems. You will probably have to change the paths for | |
| 433 LIBPATH and INCLUDEPATH in the start of the Makefile. You will get two | |
| 434 warnings which can be ignored (one about _chmod and one about precompiled | |
| 435 header files). | |
| 436 | |
| 437 The "spawno" library by Ralf Brown was used in order to free memory when Vim | |
| 438 starts a shell or other external command. Only about 200 bytes are taken from | |
| 439 conventional memory. When recompiling get the spawno library from Simtel, | |
| 440 directory "msdos/c". It is called something like "spwno413.zip". Or follow | |
| 441 the instructions in the Makefile to remove the library. | |
| 442 | |
| 443 The Turbo C Makefile has not been tested much lately. It is included for those | |
| 444 that don't have C++. You may need to make a few changes to get it to work. | |
| 445 | |
| 446 DJGPP needs to be installed properly to compile Vim; you need a lot of things | |
| 447 before it works. When your setup is OK, Vim should compile with just one | |
| 448 warning (about an argument to signal()). | |
| 449 | |
| 450 Make_bc5.mak is for those that have Borland C++ 5.0 or later. At the top of | |
| 451 the file, there are some variables you can change to make either a 32-bit | |
| 452 Windows exe (GUI or console mode), or a 16-bit MS-DOS version. | |
| 39 | 453 NOTE: multi-byte support is broken in the Borland libraries, not everything |
| 454 will work properly! Esp. handling multi-byte file names. | |
| 7 | 455 |
| 2965 | 456 If you get all kinds of strange error messages when compiling, try changing |
| 457 the file format from "unix" to "dos". | |
| 2951 | 458 |
| 459 | |
| 460 10. Installing after building from sources | |
| 461 ========================================== | |
| 462 | |
| 463 [provided by Michael Soyka] | |
| 464 | |
| 465 After you've built the Vim binaries as described above, you're ready to | |
| 466 install Vim on your system. However, if you've obtained the Vim sources | |
| 467 using Mercurial or by downloading them as a unix tar file, you must first | |
| 468 create a "vim73" directory. If you instead downloaded the sources as | |
| 469 zip files, you can skip this setup as the zip archives already have the | |
| 470 correct directory structure. | |
| 471 | |
| 472 A. Create a Vim "runtime" subdirectory named "vim73" | |
| 473 ----------------------------------------------------- | |
| 474 If you obtained your Vim sources as zip files, you can skip this step. | |
| 475 Otherwise, continue reading. | |
| 476 | |
| 477 Go to the directory that contains the Vim "src" and "runtime" | |
| 478 directories and create a new subdirectory named "vim73". | |
| 479 | |
| 480 Copy the "runtime" files into "vim73": | |
| 481 copy runtime\* vim73 | |
| 482 | |
| 483 B. Copy the new binaries into the "vim73" directory | |
| 484 ---------------------------------------------------- | |
| 485 Regardless of how you installed the Vim sources, you need to copy the | |
| 486 new binaries you created above into "vim73": | |
| 487 | |
| 488 copy src\*.exe vim73 | |
| 489 copy src\GvimExt\gvimext.dll vim73 | |
| 490 copy src\xxd\xxd.exe vim73 | |
| 491 | |
| 492 C. Move the "vim73" directory into the Vim installation subdirectory | |
| 493 --------------------------------------------------------------------- | |
| 494 Move the "vim73" subdirectory into the subdirectory where you want Vim | |
| 495 to be installed. Typically, this subdirectory will be named "vim". | |
| 496 If you already have a "vim73" subdirectory in "vim", delete it first | |
| 2965 | 497 by running its uninstal.exe program. |
| 2951 | 498 |
| 499 D. Install Vim | |
| 500 --------------- | |
| 501 "cd" to your Vim installation subdirectory "vim\vim73" and run the | |
| 502 "install.exe" program. It will ask you a number of questions about | |
| 503 how you would like to have your Vim setup. Among these are: | |
| 504 - You can tell it to write a "_vimrc" file with your preferences in the | |
| 505 parent directory. | |
| 506 - It can also install an "Edit with Vim" entry in the Windows Explorer | |
| 507 popup menu. | |
| 508 - You can have it create batch files, so that you can run Vim from the | |
| 509 console or in a shell. You can select one of the directories in your | |
| 510 PATH or add the directory to PATH using the Windows Control Panel. | |
| 511 - Create entries for Vim on the desktop and in the Start menu. | |
| 512 | |
| 513 Happy Vimming! |