Mercurial > vim
view READMEdir/README_ami.txt @ 29163:9288c636ffa5 v8.2.5101
patch 8.2.5101: MS-Windows with MinGW: $CC may be "cc" instead of "gcc"
Commit: https://github.com/vim/vim/commit/cf65d88ff844f042337dfd043e6e98f3b9270577
Author: Yegappan Lakshmanan <yegappan@yahoo.com>
Date: Wed Jun 15 18:31:45 2022 +0100
patch 8.2.5101: MS-Windows with MinGW: $CC may be "cc" instead of "gcc"
Problem: MS-Windows with MinGW: $CC may be "cc" instead of "gcc".
Solution: Set $CC if it is not matching "clang". (Yegappan Lakshmanan,
closes #10578)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 15 Jun 2022 19:45:04 +0200 |
parents | af69c9335223 |
children | f8116058ca76 |
line wrap: on
line source
README_ami.txt for version 8.2 of Vim: Vi IMproved. This file explains the installation of Vim on Amiga systems. See README.txt for general information about Vim. Unpack the distributed files in the place where you want to keep them. It is wise to have a "vim" directory to keep your vimrc file and any other files you change. The distributed files go into a subdirectory. This way you can easily upgrade to a new version. For example: dh0:editors/vim contains your vimrc and modified files dh0:editors/vim/vim54 contains the Vim version 5.4 distributed files dh0:editors/vim/vim55 contains the Vim version 5.5 distributed files You would then unpack the archives like this: cd dh0:editors tar xf t:vim82bin.tar tar xf t:vim82rt.tar Set the $VIM environment variable to point to the top directory of your Vim files. For the above example: set VIM=dh0:editors/vim Vim version 5.4 will look for your vimrc file in $VIM, and for the runtime files in $VIM/vim54. See ":help $VIM" for more information. Make sure the Vim executable is in your search path. Either copy the Vim executable to a directory that is in your search path, or (preferred) modify the search path to include the directory where the Vim executable is.