Update runtime files.

This commit is contained in:
Bram Moolenaar
2020-01-14 19:29:13 +01:00
parent ee93b737aa
commit 8024f93636
31 changed files with 183 additions and 235 deletions

View File

@ -33,12 +33,11 @@ Contents:
10. Building with Perl support
11. Building with Ruby support
12. Building with Tcl support
13. Building with Terminal support
14. Building with DirectX (DirectWrite) support
15. Windows 3.1
16. MS-DOS
13. Building with DirectX (DirectWrite) support
14. Windows 3.1
15. MS-DOS
17. Installing after building from sources
16. Installing after building from sources
The currently recommended way (that means it has been verified to work) is
@ -889,23 +888,7 @@ Or when using MinGW (as one line):
TCL=C:/Tcl86 DYNAMIC_TCL=yes TCL_VER=86 TCL_VER_LONG=8.6
13. Building with Terminal support
==================================
Vim with Terminal support can be built with either MSVC, MinGW or Cygwin.
This uses the included libvterm and winpty. No extra header files or
libraries are needed for building. Just set TERMINAL to yes.
E.g. When using MSVC:
nmake -f Make_mvc.mak TERMINAL=yes
Or when using MinGW:
mingw32-make -f Make_ming.mak TERMINAL=yes
14. Building with DirectX (DirectWrite) support
13. Building with DirectX (DirectWrite) support
===============================================
Vim with DirectX (DirectWrite) support can be built with either MSVC or MinGW.
@ -939,20 +922,20 @@ Just set DIRECTX to yes:
mingw32-make -f Make_ming.mak DIRECTX=yes
15. Windows 3.1x
14. Windows 3.1x
================
The Windows 3.1x support was removed in patch 7.4.1364.
16. MS-DOS
15. MS-DOS
==========
The MS-DOS support was removed in patch 7.4.1399. Only very old Vim versions
work on MS-DOS because of the limited amount of memory available.
17. Installing after building from sources
16. Installing after building from sources
==========================================
[provided by Michael Soyka, updated by Ken Takata]
@ -960,44 +943,44 @@ work on MS-DOS because of the limited amount of memory available.
After you've built the Vim binaries as described above, you're ready to
install Vim on your system. However, if you've obtained the Vim sources
using Git, Mercurial or by downloading them as a unix tar file, you must
first create a "vim81" directory. If you instead downloaded the sources as
first create a "vim82" directory. If you instead downloaded the sources as
zip files, you can skip this setup as the zip archives already have the
correct directory structure.
A. Create a Vim "runtime" subdirectory named "vim81"
A. Create a Vim "runtime" subdirectory named "vim82"
-----------------------------------------------------
If you obtained your Vim sources as zip files, you can skip this step.
Otherwise, continue reading.
Go to the directory that contains the Vim "src" and "runtime"
directories and create a new subdirectory named "vim81".
directories and create a new subdirectory named "vim82".
Copy the "runtime" files into "vim81":
copy runtime\* vim81
Copy the "runtime" files into "vim82":
copy runtime\* vim82
B. Copy the new binaries into the "vim81" directory
B. Copy the new binaries into the "vim82" directory
----------------------------------------------------
Regardless of how you installed the Vim sources, you need to copy the
new binaries you created above into "vim81":
new binaries you created above into "vim82":
copy src\*.exe vim81
copy src\tee\tee.exe vim81
copy src\xxd\xxd.exe vim81
copy src\*.exe vim82
copy src\tee\tee.exe vim82
copy src\xxd\xxd.exe vim82
To install the "Edit with Vim" popup menu, you need both 32-bit and 64-bit
versions of gvimext.dll. They should be copied to "vim81\GvimExt32" and
"vim81\GvimExt64" respectively.
versions of gvimext.dll. They should be copied to "vim82\GvimExt32" and
"vim82\GvimExt64" respectively.
First, build the 32-bit version, then:
mkdir vim81\GvimExt32
copy src\GvimExt\gvimext.dll vim81\GvimExt32
mkdir vim82\GvimExt32
copy src\GvimExt\gvimext.dll vim82\GvimExt32
Next, clean the 32-bit version and build the 64-bit version, then:
mkdir vim81\GvimExt64
copy src\GvimExt\gvimext.dll vim81\GvimExt64
mkdir vim82\GvimExt64
copy src\GvimExt\gvimext.dll vim82\GvimExt64
C. Copy gettext and iconv DLLs into the "vim81" directory
C. Copy gettext and iconv DLLs into the "vim82" directory
----------------------------------------------------------
Get gettext and iconv DLLs from the following site:
https://github.com/mlocati/gettext-iconv-windows/releases
@ -1005,7 +988,7 @@ correct directory structure.
Download the files gettextX.X.X.X-iconvX.XX-shared-{32,64}.zip, extract
DLLs and place them as follows:
vim81\
vim82\
| libintl-8.dll
| libiconv-2.dll
| libgcc_s_sjlj-1.dll (only for 32-bit)
@ -1019,18 +1002,18 @@ correct directory structure.
libintl-8.dll
libiconv-2.dll
The DLLs in the "vim81" should be the same bitness with the (g)vim.exe.
The DLLs in the "vim82" should be the same bitness with the (g)vim.exe.
D. Move the "vim81" directory into the Vim installation subdirectory
D. Move the "vim82" directory into the Vim installation subdirectory
---------------------------------------------------------------------
Move the "vim81" subdirectory into the subdirectory where you want Vim
Move the "vim82" subdirectory into the subdirectory where you want Vim
to be installed. Typically, this subdirectory will be named "vim".
If you already have a "vim81" subdirectory in "vim", delete it first
If you already have a "vim82" subdirectory in "vim", delete it first
by running its uninstall.exe program.
E. Install Vim
---------------
"cd" to your Vim installation subdirectory "vim\vim81" and run the
"cd" to your Vim installation subdirectory "vim\vim82" and run the
"install.exe" program. It will ask you a number of questions about
how you would like to have your Vim setup. Among these are:
- You can tell it to write a "_vimrc" file with your preferences in the