Mercurial > vim

comparison src/INSTALLpc.txt @ 856:8cd729851562 v7.0g

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated for version 7.0g
author vimboss
date Sun, 30 Apr 2006 18:54:39 +0000
parents 8e5830943bff
children 9fbb40a1228a
comparison
equal deleted inserted replaced
855:d2a4f08396fe 856:8cd729851562
41 41
42 To build Vim from the command line with MSVC, use Make_mvc.mak. 42 To build Vim from the command line with MSVC, use Make_mvc.mak.
43 Visual Studio installed a batch file called vcvars32.bat, which you must 43 Visual Studio installed a batch file called vcvars32.bat, which you must
44 run to set up paths for nmake and MSVC. 44 run to set up paths for nmake and MSVC.
45 45
46 nmake -f Make_mvc.mak console Win32 SDK or Microsoft Visual C++ 46 nmake -f Make_mvc.mak console Win32 SDK or Microsoft Visual C++
47 nmake -f Make_mvc.mak GUI=yes GUI Microsoft Visual C++ 47 nmake -f Make_mvc.mak GUI=yes GUI Microsoft Visual C++
48 nmake -f Make_mvc.mak OLE=yes OLE Microsoft Visual C++ 48 nmake -f Make_mvc.mak OLE=yes OLE Microsoft Visual C++
49 nmake -f Make_mvc.mak PERL=C:\Perl PYTHON=C:\Python etc. 49 nmake -f Make_mvc.mak PERL=C:\Perl PYTHON=C:\Python etc.
50 Perl, Python, etc. 50 Perl, Python, etc.
51 51
52 Make_mvc.mak allows a Vim to be built with various different features and 52 Make_mvc.mak allows a Vim to be built with various different features and
53 debug support. Debugging with MS Devstudio is provided by Make_dvc.mak. 53 debug support. Debugging with MS Devstudio is provided by Make_dvc.mak.
54 For a description of the use of Make_dvc.mak, look in Make_mvc.mak. 54 For a description of the use of Make_dvc.mak, look in Make_mvc.mak.
55 55
59 To build Vim from within the Visual Studio IDE, open the Make_ivc.mak project. 59 To build Vim from within the Visual Studio IDE, open the Make_ivc.mak project.
60 (Note: Make_ivc.mak is not as rich as Make_mvc.mak, which allows for 60 (Note: Make_ivc.mak is not as rich as Make_mvc.mak, which allows for
61 far more configuration.) Make_ivc.mak can also be built with nmake. 61 far more configuration.) Make_ivc.mak can also be built with nmake.
62 62
63 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim" 63 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim"
64 GUI Microsoft Visual C++ 4.x or later 64 GUI Microsoft Visual C++ 4.x or later
65 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim OLE" 65 nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim OLE"
66 OLE Microsoft Visual C++ 4.x or later 66 OLE Microsoft Visual C++ 4.x or later
67 67
68 See the specific files for comments and options. 68 See the specific files for comments and options.
69 69
70 These files have been supplied by George V. Reilly, Ben Singer, Ken Scott and 70 These files have been supplied by George V. Reilly, Ben Singer, Ken Scott and
71 Ron Aaron; they have been tested. 71 Ron Aaron; they have been tested.
92 free C compilers for Win32.) 92 free C compilers for Win32.)
93 93
94 To compile Vim using the VC2003 Toolkit and Make_mvc.mak, you must first 94 To compile Vim using the VC2003 Toolkit and Make_mvc.mak, you must first
95 execute the following commands in a cmd.exe window (the msvcsetup.bat batch 95 execute the following commands in a cmd.exe window (the msvcsetup.bat batch
96 file can be used): 96 file can be used):
97 97
98 set PATH=%SystemRoot%\Microsoft.NET\Framework\v1.1.4322;%PATH% 98 set PATH=%SystemRoot%\Microsoft.NET\Framework\v1.1.4322;%PATH%
99 call "%VCToolkitInstallDir%vcvars32.bat" 99 call "%VCToolkitInstallDir%vcvars32.bat"
100 set MSVCVer=7.1 100 set MSVCVer=7.1
101 call "%ProgramFiles%\Microsoft Platform SDK\SetEnv.Cmd" 101 call "%ProgramFiles%\Microsoft Platform SDK\SetEnv.Cmd"
102 set LIB=%ProgramFiles%\Microsoft Visual Studio .NET 2003\Vc7\lib;%LIB% 102 set LIB=%ProgramFiles%\Microsoft Visual Studio .NET 2003\Vc7\lib;%LIB%
103 103
104 Now you can build Vim with Make_mvc.mak. 104 Now you can build Vim with Make_mvc.mak.
105 105
106 106
107 Getting the Windows Platform SDK *ms-platform-sdk* 107 Getting the Windows Platform SDK *ms-platform-sdk*
108 108
109 You will also need a copy of the Windows Platform SDK from 109 You will also need a copy of the Windows Platform SDK from
110 http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ 110 http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
111 Specifically, you need the Windows Core SDK subset of the Platform SDK, 111 Specifically, you need the Windows Core SDK subset of the Platform SDK,
112 which contains the Windows headers and libraries. 112 which contains the Windows headers and libraries.
120 http://windowsupdate.microsoft.com/ 120 http://windowsupdate.microsoft.com/
121 This is needed to install |dotnet-1.1-sdk|. It also contains cvtres.exe, 121 This is needed to install |dotnet-1.1-sdk|. It also contains cvtres.exe,
122 which is needed to link Vim. 122 which is needed to link Vim.
123 123
124 124
125 Getting the .NET Framework 1.1 SDK *dotnet-1.1-sdk* 125 Getting the .NET Framework 1.1 SDK *dotnet-1.1-sdk*
126 126
127 You need the .NET Framework 1.1 SDK from 127 You need the .NET Framework 1.1 SDK from
128 http://www.microsoft.com/downloads/details.aspx?familyid=9b3a2ca6-3647-4070-9f41-a333c6b9181d 128 http://www.microsoft.com/downloads/details.aspx?familyid=9b3a2ca6-3647-4070-9f41-a333c6b9181d
129 This contains some additional libraries needed to compile Vim, 129 This contains some additional libraries needed to compile Vim,
130 such as msvcrt.lib. You must install |dotnet-1.1-redist| before 130 such as msvcrt.lib. You must install |dotnet-1.1-redist| before
131 installing the .NET 1.1 SDK. 131 installing the .NET 1.1 SDK.
132 132
133 133
134 Getting the WinDbg debugger *windbg-download* 134 Getting the WinDbg debugger *windbg-download*
135 135
136 The Debugging Tools for Windows can be downloaded from 136 The Debugging Tools for Windows can be downloaded from
137 http://www.microsoft.com/whdc/devtools/debugging/default.mspx 137 http://www.microsoft.com/whdc/devtools/debugging/default.mspx
138 This includes the WinDbg debugger, which you will want if you ever need 138 This includes the WinDbg debugger, which you will want if you ever need
139 to debug Vim itself. An earlier version of the Debugging Tools 139 to debug Vim itself. An earlier version of the Debugging Tools
240 [Update of 1) needs to be verified] 240 [Update of 1) needs to be verified]
241 241
242 If you like, you can compile the 'mingw' Win32 version from the comfort of 242 If you like, you can compile the 'mingw' Win32 version from the comfort of
243 your Linux (or other unix) box. To do this, you need to follow a few steps: 243 your Linux (or other unix) box. To do this, you need to follow a few steps:
244 1) Install the mingw32 cross-compiler. See 244 1) Install the mingw32 cross-compiler. See
245 http://www.libsdl.org/extras/win32/cross/README.txt 245 http://www.libsdl.org/extras/win32/cross/README.txt
246 2) get the *unix* version of the vim sources 246 2) get the *unix* version of the vim sources
247 3) in 'Make_ming.mak', set 'CROSS' to '1' instead of '0'. 247 3) in 'Make_ming.mak', set 'CROSS' to '1' instead of '0'.
248 4) make -f Make_ming.mak gvim.exe 248 4) make -f Make_ming.mak gvim.exe
249 249
250 Now you have created the Windows binary from your Linux box! Have fun... 250 Now you have created the Windows binary from your Linux box! Have fun...
315 315
316 316
317 8. Windows 3.1x 317 8. Windows 3.1x
318 =============== 318 ===============
319 319
320 make -f Make_w16.mak 16 bit, Borland C++ 5.0 320 make -f Make_w16.mak 16 bit, Borland C++ 5.0
321 321
322 Warning: Be sure to use the right make.exe. It should be Borland make. 322 Warning: Be sure to use the right make.exe. It should be Borland make.
323 323
324 You will almost certainly have to change the paths for libs and include files 324 You will almost certainly have to change the paths for libs and include files
325 in the Makefile. Look for "D:\BC5" and "ctl3dv2". You will get a number of 325 in the Makefile. Look for "D:\BC5" and "ctl3dv2". You will get a number of
338 ========= 338 =========
339 339
340 Summary: 340 Summary:
341 ren Make_bc3.mak Makefile; make 16 bit, Borland C++ and Turbo C++ 341 ren Make_bc3.mak Makefile; make 16 bit, Borland C++ and Turbo C++
342 ren Make_tcc.mak Makefile; make 16 bit, Turbo C 342 ren Make_tcc.mak Makefile; make 16 bit, Turbo C
343 make -f Make_djg.mak 32 bit, DJGPP 2.0 343 make -f Make_djg.mak 32 bit, DJGPP 2.0
344 make -f Make_bc5.mak 32 bit, Borland C++ 5.x (edit it to 344 make -f Make_bc5.mak 32 bit, Borland C++ 5.x (edit it to
345 define DOS) 345 define DOS)
346 346
347 Warning: Be sure to use the right make.exe. Microsoft C make doesn't work; 347 Warning: Be sure to use the right make.exe. Microsoft C make doesn't work;
348 Borland make only works with Make_bc3.mak, Make_bc5.mak and Make_tcc.mak; 348 Borland make only works with Make_bc3.mak, Make_bc5.mak and Make_tcc.mak;
349 DJGPP/GNU make must be used for Make_djg.mak. 349 DJGPP/GNU make must be used for Make_djg.mak.
350 350