Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 487 lines (343 sloc) 18.306 kB
e5c6ef7 updated for version 7.0001
vimboss authored
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
852a687 updated for version 7.0216
vimboss authored
6 More information can be found here: (Very stale now.)
e5c6ef7 updated for version 7.0001
vimboss authored
7
852a687 updated for version 7.0216
vimboss authored
8 http://mywebpage.netscape.com/sharppeople/vim/howto/
e5c6ef7 updated for version 7.0001
vimboss authored
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
7c4547b updated for version 7.3.248
Bram Moolenaar authored
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)
852a687 updated for version 7.0216
vimboss authored
17
e5c6ef7 updated for version 7.0001
vimboss authored
18
19 Contents:
852a687 updated for version 7.0216
vimboss authored
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
e5c6ef7 updated for version 7.0001
vimboss authored
29
7c4547b updated for version 7.3.248
Bram Moolenaar authored
30 10. Installing after building from sources
31
32
7a75fec updated for version 7.2b-000
vimboss authored
33 The currently preferred method is using the free Visual C++ Toolkit 2008
d61d77b updated for version 7.3.209
Bram Moolenaar authored
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|.
e5c6ef7 updated for version 7.0001
vimboss authored
37
38
852a687 updated for version 7.0216
vimboss authored
39 1. Microsoft Visual C++
40 =======================
e5c6ef7 updated for version 7.0001
vimboss authored
41
852a687 updated for version 7.0216
vimboss authored
42 Visual Studio
43 -------------
e5c6ef7 updated for version 7.0001
vimboss authored
44
255571d updated for version 7.1-321
vimboss authored
45 Building with Visual Studio (VS 98, VS .NET, VS .NET 2003, VS 2005, and VS 2008)
852a687 updated for version 7.0216
vimboss authored
46 is straightforward. (These instructions should also work for VS 4 and VS 5.)
e5c6ef7 updated for version 7.0001
vimboss authored
47
393f45e Update runtime files.
Bram Moolenaar authored
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
852a687 updated for version 7.0216
vimboss authored
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.
e5c6ef7 updated for version 7.0001
vimboss authored
55
c7c9443 updated for version 7.0g
vimboss authored
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++
852a687 updated for version 7.0216
vimboss authored
59 nmake -f Make_mvc.mak PERL=C:\Perl PYTHON=C:\Python etc.
c7c9443 updated for version 7.0g
vimboss authored
60 Perl, Python, etc.
e5c6ef7 updated for version 7.0001
vimboss authored
61
852a687 updated for version 7.0216
vimboss authored
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.
e5c6ef7 updated for version 7.0001
vimboss authored
65
852a687 updated for version 7.0216
vimboss authored
66 For compiling Gvim with IME support on far-east Windows, add IME=yes
67 to the parameters you pass to Make_mvc.mak.
e5c6ef7 updated for version 7.0001
vimboss authored
68
852a687 updated for version 7.0216
vimboss authored
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"
c7c9443 updated for version 7.0g
vimboss authored
74 GUI Microsoft Visual C++ 4.x or later
852a687 updated for version 7.0216
vimboss authored
75 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim OLE"
c7c9443 updated for version 7.0g
vimboss authored
76 OLE Microsoft Visual C++ 4.x or later
e5c6ef7 updated for version 7.0001
vimboss authored
77
852a687 updated for version 7.0216
vimboss authored
78 See the specific files for comments and options.
e5c6ef7 updated for version 7.0001
vimboss authored
79
852a687 updated for version 7.0216
vimboss authored
80 These files have been supplied by George V. Reilly, Ben Singer, Ken Scott and
81 Ron Aaron; they have been tested.
e5c6ef7 updated for version 7.0001
vimboss authored
82
83
7a75fec updated for version 7.2b-000
vimboss authored
84 Visual C++ Toolkit 2003 *msvc-2003-toolkit*
852a687 updated for version 7.0216
vimboss authored
85 -----------------------
e5c6ef7 updated for version 7.0001
vimboss authored
86
7a75fec updated for version 7.2b-000
vimboss authored
87 You could download the Microsoft Visual C++ Toolkit 2003 from
852a687 updated for version 7.0216
vimboss authored
88 http://msdn.microsoft.com/visualc/vctoolkit2003/
7a75fec updated for version 7.2b-000
vimboss authored
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
852a687 updated for version 7.0216
vimboss authored
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|.
e5c6ef7 updated for version 7.0001
vimboss authored
99
045cef0 updated for version 7.1-282
vimboss authored
100 It's easier to download Visual C++ 2008 Express Edition, |msvc-2008-express|,
101 which is freely available in perpetuity.
e5c6ef7 updated for version 7.0001
vimboss authored
102
852a687 updated for version 7.0216
vimboss authored
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.)
e5c6ef7 updated for version 7.0001
vimboss authored
107
852a687 updated for version 7.0216
vimboss authored
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):
c7c9443 updated for version 7.0g
vimboss authored
111
852a687 updated for version 7.0216
vimboss authored
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%
e5c6ef7 updated for version 7.0001
vimboss authored
117
852a687 updated for version 7.0216
vimboss authored
118 Now you can build Vim with Make_mvc.mak.
e5c6ef7 updated for version 7.0001
vimboss authored
119
120
c7c9443 updated for version 7.0g
vimboss authored
121 Getting the Windows Platform SDK *ms-platform-sdk*
e5c6ef7 updated for version 7.0001
vimboss authored
122
852a687 updated for version 7.0216
vimboss authored
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.
e5c6ef7 updated for version 7.0001
vimboss authored
127
128
852a687 updated for version 7.0216
vimboss authored
129 Getting the .NET Framework 1.1 Runtime *dotnet-1.1-redist*
e5c6ef7 updated for version 7.0001
vimboss authored
130
852a687 updated for version 7.0216
vimboss authored
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.
e5c6ef7 updated for version 7.0001
vimboss authored
137
138
c7c9443 updated for version 7.0g
vimboss authored
139 Getting the .NET Framework 1.1 SDK *dotnet-1.1-sdk*
e5c6ef7 updated for version 7.0001
vimboss authored
140
852a687 updated for version 7.0216
vimboss authored
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.
e5c6ef7 updated for version 7.0001
vimboss authored
146
147
c7c9443 updated for version 7.0g
vimboss authored
148 Getting the WinDbg debugger *windbg-download*
852a687 updated for version 7.0216
vimboss authored
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|.
e5c6ef7 updated for version 7.0001
vimboss authored
155
852a687 updated for version 7.0216
vimboss authored
156
255571d updated for version 7.1-321
vimboss authored
157 Visual C++ 2005 Express Edition *msvc-2005-express*
852a687 updated for version 7.0216
vimboss authored
158 -------------------------------
159
5723a0e updated for version 7.0e04
vimboss authored
160 Visual C++ 2005 Express Edition can be downloaded for free from:
852a687 updated for version 7.0216
vimboss authored
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
167
168
045cef0 updated for version 7.1-282
vimboss authored
169 Visual C++ 2008 Express Edition *msvc-2008-express*
170 -------------------------------
171
172 Visual C++ 2008 Express Edition can be downloaded for free from:
3859400 Improve the MS-Windows installer.
Bram Moolenaar authored
173 http://www.microsoft.com/express/downloads/
174 This includes the IDE and the debugger.
175
176 To set the environment execute the msvc2008.bat script. You can then build
177 Vim with Make_mvc.mak.
178
393f45e Update runtime files.
Bram Moolenaar authored
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
3859400 Improve the MS-Windows installer.
Bram Moolenaar authored
183
184 Visual C++ 2010 Express Edition *msvc-2010-express*
185 -------------------------------
186
187 Visual C++ 2010 Express Edition can be downloaded for free from:
d87f8c5 updated for version 7.2a
vimboss authored
188 http://www.microsoft.com/express/vc/Default.aspx
189 This includes the IDE and the debugger.
255571d updated for version 7.1-321
vimboss authored
190
d61d77b updated for version 7.3.209
Bram Moolenaar authored
191 To set the environment execute the msvc2010.bat script. You can then build
d87f8c5 updated for version 7.2a
vimboss authored
192 Vim with Make_mvc.mak.
045cef0 updated for version 7.1-282
vimboss authored
193
194
852a687 updated for version 7.0216
vimboss authored
195 2. MinGW
e5c6ef7 updated for version 7.0001
vimboss authored
196 ========
197
198 (written by Ron Aaron: <ronaharon@yahoo.com>)
199
852a687 updated for version 7.0216
vimboss authored
200 This is about how to produce a Win32 binary of gvim with MinGW.
e5c6ef7 updated for version 7.0001
vimboss authored
201
202 First, you need to get the 'mingw32' compiler, which is free for the download
203 at:
204
852a687 updated for version 7.0216
vimboss authored
205 http://www.mingw.org/
e5c6ef7 updated for version 7.0001
vimboss authored
206
207 Once you have downloaded the compiler binaries, unpack them on your hard disk
208 somewhere, and put them on your PATH. If you are on Win95/98 you can edit
209 your AUTOEXEC.BAT file with a line like:
210
852a687 updated for version 7.0216
vimboss authored
211 set PATH=C:\GCC-2.95.2\BIN;%PATH%
e5c6ef7 updated for version 7.0001
vimboss authored
212
852a687 updated for version 7.0216
vimboss authored
213 or on NT/2000/XP, go to the Control Panel, (Performance and Maintenance),
214 System, Advanced, and edit the environment from there.
e5c6ef7 updated for version 7.0001
vimboss authored
215
852a687 updated for version 7.0216
vimboss authored
216 Test if gcc is on your path. From a CMD (or COMMAND on '95/98) window:
e5c6ef7 updated for version 7.0001
vimboss authored
217
852a687 updated for version 7.0216
vimboss authored
218 C:\> gcc --version
219 2.95.2
e5c6ef7 updated for version 7.0001
vimboss authored
220
852a687 updated for version 7.0216
vimboss authored
221 C:\> make --version
222 GNU Make version 3.77 (...etc...)
e5c6ef7 updated for version 7.0001
vimboss authored
223
224 Now you are ready to rock 'n' roll. Unpack the vim sources (look on
225 www.vim.org for exactly which version of the vim files you need).
226
227 Change directory to 'vim\src':
228
852a687 updated for version 7.0216
vimboss authored
229 C:\> cd vim\src
230 C:\VIM\SRC>
e5c6ef7 updated for version 7.0001
vimboss authored
231
232 and you type:
233
852a687 updated for version 7.0216
vimboss authored
234 make -f Make_ming.mak gvim.exe
e5c6ef7 updated for version 7.0001
vimboss authored
235
236 After churning for a while, you will end up with 'gvim.exe' in the 'vim\src'
237 directory.
238
239 You should not need to do *any* editing of any files to get vim compiled this
240 way. If, for some reason, you want the console-mode-only version of vim (this
a3a0af3 Updated runtime an documentation files.
Bram Moolenaar authored
241 is NOT recommended on Win32, especially on '95/'98!!!), you can use:
6ef6c58 Minor text file updates.
Bram Moolenaar authored
242
243 make -f Make_ming.mak GUI=no vim.exe
e5c6ef7 updated for version 7.0001
vimboss authored
244
245 If you are dismayed by how big the EXE is, I strongly recommend you get 'UPX'
246 (also free!) and compress the file (typical compression is 50%). UPX can be
247 found at
852a687 updated for version 7.0216
vimboss authored
248 http://www.upx.org/
e5c6ef7 updated for version 7.0001
vimboss authored
249
1305959 updated for version 7.3.460
Bram Moolenaar authored
250 As of 2011, UPX still does not support compressing 64-bit EXE's; if you have
251 built a 64-bit vim then an alternative to UPX is 'MPRESS'. MPRESS can be found
252 at:
253 http://www.matcode.com/mpress.htm
254
255
852a687 updated for version 7.0216
vimboss authored
256 ADDITION: NLS support with MinGW
e5c6ef7 updated for version 7.0001
vimboss authored
257
258 (by Eduardo F. Amatria <eferna1@platea.pntic.mec.es>)
259
260 If you want National Language Support, read the file src/po/README_mingw.txt.
261 You need to uncomment lines in Make_ming.mak to have NLS defined.
262
263
852a687 updated for version 7.0216
vimboss authored
264 3. Cygwin
265 =========
266
267 Use Make_cyg.mak with Cygwin's GCC. See
268 http://users.skynet.be/antoine.mechelynck/vim/compile.htm
269
270 The Cygnus one many not fully work yet.
271 With Cygnus gcc you can use the Unix Makefile instead (you need to get the
272 Unix archive then). Then you get a Cygwin application (feels like Vim is
06bd94b updated for version 7.2.372
Bram Moolenaar authored
273 running on Unix), while with Make_cyg.mak you get a Windows application (like
852a687 updated for version 7.0216
vimboss authored
274 with the other makefiles).
275
276
277 4. Borland
278 ===========
279
280 Use Make_bc5.mak with Borland C++ 5.x. See
281 http://users.skynet.be/antoine.mechelynck/vim/compile.htm
282
283
284 5. Cross compiling for Win32 from a Linux machine
e5c6ef7 updated for version 7.0001
vimboss authored
285 =================================================
286
852a687 updated for version 7.0216
vimboss authored
287 [Update of 1) needs to be verified]
e5c6ef7 updated for version 7.0001
vimboss authored
288
289 If you like, you can compile the 'mingw' Win32 version from the comfort of
290 your Linux (or other unix) box. To do this, you need to follow a few steps:
852a687 updated for version 7.0216
vimboss authored
291 1) Install the mingw32 cross-compiler. See
6ef6c58 Minor text file updates.
Bram Moolenaar authored
292 http://www.mingw.org/wiki/LinuxCrossMinGW
c7c9443 updated for version 7.0g
vimboss authored
293 http://www.libsdl.org/extras/win32/cross/README.txt
d87f8c5 updated for version 7.2a
vimboss authored
294 2) Get and unpack both the Unix sources and the extra archive
295 3) in 'Make_ming.mak', set 'CROSS' to 'yes' instead of 'no'.
296 Make further changes to 'Make_ming.mak' as you wish.
6ef6c58 Minor text file updates.
Bram Moolenaar authored
297 If your cross-compiler prefix differs from the predefined value,
298 set 'CROSS_COMPILE' corresponding.
852a687 updated for version 7.0216
vimboss authored
299 4) make -f Make_ming.mak gvim.exe
e5c6ef7 updated for version 7.0001
vimboss authored
300
301 Now you have created the Windows binary from your Linux box! Have fun...
302
852a687 updated for version 7.0216
vimboss authored
303
304 6. Building with Python support
305 ===============================
e5c6ef7 updated for version 7.0001
vimboss authored
306
393f45e Update runtime files.
Bram Moolenaar authored
307 For building with MSVC 2008 the "Windows Installer" from www.python.org
308 works fine.
309
310 (rest written by Ron Aaron: <ronaharon@yahoo.com>)
e5c6ef7 updated for version 7.0001
vimboss authored
311
393f45e Update runtime files.
Bram Moolenaar authored
312 Building with the mingw32 compiler, and the ActiveState ActivePython:
e5c6ef7 updated for version 7.0001
vimboss authored
313 http://www.ActiveState.com/Products/ActivePython/
314
315 After installing the ActivePython, you will have to create a 'mingw32'
316 'libpython20.a' to link with:
317 cd $PYTHON/libs
318 pexports python20.dll > python20.def
319 dlltool -d python20.def -l libpython20.a
320
321 Once that is done, edit the 'Make_ming.mak' so the PYTHON variable points to
322 the root of the Python installation (C:\Python20, for example). If you are
323 cross-compiling on Linux with the mingw32 setup, you need to also convert all
324 the 'Include' files to *unix* line-endings. This bash command will do it
325 easily:
326 for fil in *.h ; do vim -e -c 'set ff=unix|w|q' $fil
327
328 Now just do:
329 make -f Make_ming.mak gvim.exe
330
331 and you will end up with a Python-enabled, Win32 version. Enjoy!
8183e77 updated for version 7.0046
vimboss authored
332
852a687 updated for version 7.0216
vimboss authored
333
334 7. Building with MzScheme support
335 =================================
8183e77 updated for version 7.0046
vimboss authored
336
337 (written by Sergey Khorev <sergey.khorev@gmail.com>)
338
339 Vim with MzScheme (http://www.plt-scheme.org/software/mzscheme) support can
340 be built with either MSVC, or MinGW, or Cygwin. Supported versions are 205 and
341 above (including 299 and 30x series).
342
343 The MSVC build is quite straightforward. Simply invoke (in one line)
344 nmake -fMake_mvc.mak MZSCHEME=<Path-to-MzScheme>
345 [MZSCHEME_VER=<MzScheme-version>] [DYNAMIC_MZSCHEME=<yes or no>]
346 where <MzScheme-version> is the last seven characters from MzScheme dll name
347 (libmzschXXXXXXX.dll).
348 If DYNAMIC_MZSCHEME=yes, resulting executable will not depend on MzScheme
349 DLL's, but will load them in runtime on demand.
350
351 Building dynamic MzScheme support on MinGW and Cygwin is similar. Take into
352 account that <Path-to-MzScheme> should contain slashes rather than backslashes
353 (e.g. d:/Develop/MzScheme)
354
355 "Static" MzScheme support (Vim executable will depend on MzScheme DLLs
356 explicitly) on MinGW and Cygwin requires additional step.
357
358 libmzschXXXXXXX.dll and libmzgcXXXXXXX.dll should be copied from
359 %WINDOWS%\System32 to other location (either build directory, some temporary
360 dir or even MzScheme home).
361
362 Pass that path as MZSCHEME_DLLS parameter for Make. E.g.,
852a687 updated for version 7.0216
vimboss authored
363 make -f Make_cyg.mak MZSCHEME=d:/Develop/MzScheme MZSCHEME_VER=209_000
8183e77 updated for version 7.0046
vimboss authored
364 MZSCHEME_DLLS=c:/Temp DYNAMIC_MZSCHEME=no
365
852a687 updated for version 7.0216
vimboss authored
366 After a successful build, these dlls can be freely removed, leaving them in
8183e77 updated for version 7.0046
vimboss authored
367 %WINDOWS%\System32 only.
852a687 updated for version 7.0216
vimboss authored
368
369
370 8. Windows 3.1x
371 ===============
372
c7c9443 updated for version 7.0g
vimboss authored
373 make -f Make_w16.mak 16 bit, Borland C++ 5.0
852a687 updated for version 7.0216
vimboss authored
374
375 Warning: Be sure to use the right make.exe. It should be Borland make.
376
377 You will almost certainly have to change the paths for libs and include files
378 in the Makefile. Look for "D:\BC5" and "ctl3dv2". You will get a number of
379 warnings which can be ignored ( _chmod, precompiled header files, and
380 "possibly incorrect assignment").
381
382 The makefile should also work for BC++ 4.0 and 4.5, but may need tweaking to
383 remove unsupported compiler & liker options.
384
385 For making the Win32s version, you need Microsoft Visual C++ 4.1 OR EARLIER.
386 In MSVC 4.2 support for Win32s was dropped! Use this command:
387 nmake -f Make_mvc.mak GUI=yes
388
389
390 9. MS-DOS
391 =========
392
393 Summary:
394 ren Make_bc3.mak Makefile; make 16 bit, Borland C++ and Turbo C++
395 ren Make_tcc.mak Makefile; make 16 bit, Turbo C
c7c9443 updated for version 7.0g
vimboss authored
396 make -f Make_djg.mak 32 bit, DJGPP 2.0
397 make -f Make_bc5.mak 32 bit, Borland C++ 5.x (edit it to
398 define DOS)
852a687 updated for version 7.0216
vimboss authored
399
400 Warning: Be sure to use the right make.exe. Microsoft C make doesn't work;
401 Borland make only works with Make_bc3.mak, Make_bc5.mak and Make_tcc.mak;
402 DJGPP/GNU make must be used for Make_djg.mak.
403
404 The Borland C++ compiler has been used to generate the MS-DOS executable; it
405 should work without problems. You will probably have to change the paths for
406 LIBPATH and INCLUDEPATH in the start of the Makefile. You will get two
407 warnings which can be ignored (one about _chmod and one about precompiled
408 header files).
409
410 The "spawno" library by Ralf Brown was used in order to free memory when Vim
411 starts a shell or other external command. Only about 200 bytes are taken from
412 conventional memory. When recompiling get the spawno library from Simtel,
413 directory "msdos/c". It is called something like "spwno413.zip". Or follow
414 the instructions in the Makefile to remove the library.
415
416 The Turbo C Makefile has not been tested much lately. It is included for those
417 that don't have C++. You may need to make a few changes to get it to work.
418
419 DJGPP needs to be installed properly to compile Vim; you need a lot of things
420 before it works. When your setup is OK, Vim should compile with just one
421 warning (about an argument to signal()).
422
423 Make_bc5.mak is for those that have Borland C++ 5.0 or later. At the top of
424 the file, there are some variables you can change to make either a 32-bit
425 Windows exe (GUI or console mode), or a 16-bit MS-DOS version.
426 NOTE: multi-byte support is broken in the Borland libraries, not everything
427 will work properly! Esp. handling multi-byte file names.
428
1e4ca09 Updated runtime files.
Bram Moolenaar authored
429 If you get all kinds of strange error messages when compiling, try changing
430 the file format from "unix" to "dos".
7c4547b updated for version 7.3.248
Bram Moolenaar authored
431
432
433 10. Installing after building from sources
434 ==========================================
435
436 [provided by Michael Soyka]
437
438 After you've built the Vim binaries as described above, you're ready to
439 install Vim on your system. However, if you've obtained the Vim sources
440 using Mercurial or by downloading them as a unix tar file, you must first
441 create a "vim73" directory. If you instead downloaded the sources as
442 zip files, you can skip this setup as the zip archives already have the
443 correct directory structure.
444
445 A. Create a Vim "runtime" subdirectory named "vim73"
446 -----------------------------------------------------
447 If you obtained your Vim sources as zip files, you can skip this step.
448 Otherwise, continue reading.
449
450 Go to the directory that contains the Vim "src" and "runtime"
451 directories and create a new subdirectory named "vim73".
452
453 Copy the "runtime" files into "vim73":
454 copy runtime\* vim73
455
456 B. Copy the new binaries into the "vim73" directory
457 ----------------------------------------------------
458 Regardless of how you installed the Vim sources, you need to copy the
459 new binaries you created above into "vim73":
460
461 copy src\*.exe vim73
462 copy src\GvimExt\gvimext.dll vim73
463 copy src\xxd\xxd.exe vim73
464
465 C. Move the "vim73" directory into the Vim installation subdirectory
466 ---------------------------------------------------------------------
467 Move the "vim73" subdirectory into the subdirectory where you want Vim
468 to be installed. Typically, this subdirectory will be named "vim".
469 If you already have a "vim73" subdirectory in "vim", delete it first
1e4ca09 Updated runtime files.
Bram Moolenaar authored
470 by running its uninstal.exe program.
7c4547b updated for version 7.3.248
Bram Moolenaar authored
471
472 D. Install Vim
473 ---------------
474 "cd" to your Vim installation subdirectory "vim\vim73" and run the
475 "install.exe" program. It will ask you a number of questions about
476 how you would like to have your Vim setup. Among these are:
477 - You can tell it to write a "_vimrc" file with your preferences in the
478 parent directory.
479 - It can also install an "Edit with Vim" entry in the Windows Explorer
480 popup menu.
481 - You can have it create batch files, so that you can run Vim from the
482 console or in a shell. You can select one of the directories in your
483 PATH or add the directory to PATH using the Windows Control Panel.
484 - Create entries for Vim on the desktop and in the Start menu.
485
486 Happy Vimming!
Something went wrong with that request. Please try again.