Vim Tips Wiki
(Added to Cygwin and Windows Categories ; first cleanup)
No edit summary
 
(11 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[Category:Cygwin]][[Category:Windows]]
 
 
{{review}}
 
{{review}}
  +
{{TipImported
{{Tip
 
 
|id=531
 
|id=531
  +
|previous=530
|title=1-2-3, let's make gvim.exe for free
 
  +
|next=533
|created=August 16, 2003 22:45
+
|created=2003
 
|complexity=basic
 
|complexity=basic
|author=maxiangjiang--AT--hotmail.com
+
|author=maxiangjiang
 
|version=6.0
 
|version=6.0
 
|rating=26/12
 
|rating=26/12
  +
|category1=Building Vim
|text=
 
  +
|category2=Cygwin
This tip is for those who is interested to make gvim.exe on Windows without using MSVC or BCC. The condition is that cygwin is installed. (Another tip for Windows users: cygwin makes Windows really useful!)
 
  +
|category3=Windows
 
}}
  +
{{Deprecated|The CVS server for Vim is no longer available. [[Getting the Vim source with Mercurial]] is now the recommended method, then you will need to compile as detailed in the rest of this tip}}
 
This tip is for those who are interested in building gvim.exe on Windows without using MSVC or BCC. The condition is that cygwin is installed.
   
Following is three steps (under any shell and any directory)
+
Following are the three steps (under any shell and any directory).
   
  +
<pre>
'''step 1: '''
 
cvs -z3 -d:pserver:anonymous--AT--cvs.vim.org:/cvsroot/vim co vim
+
cvs -z3 -d:pserver:anonymous@cvs.vim.org:/cvsroot/vim co vim
 
cd vim/src
 
make -f Make_cyg.mak IME=yes
  +
</pre>
   
 
I have tested under Windows 2000 and have used my own gvim.exe for months without any problem.
'''step 2: '''
 
cd vim/src
 
   
 
==Comments==
'''step 3: '''
 
 
Dan Sharp has an end-to-end solution for almost all problems for Vim compiling on Windows:
make -f Make_cyg.mak IME=yes
 
 
I have tested under Windows 2000 and have used my own gvim.exe for months without any problem.
 
 
Special thanks to Dan Sharp to develop/debug Make_cyg.mak, which make it possible.
 
 
}}
 
 
== Comments ==
 
Thanks for the useful tip. Does anyone know how to compile regular vim.exe on Windows using the g++ compiler? I prefer the non-GUI vim to gvim.
 
 
Thank you,
 
Peter
 
 
ptoennies--AT--hotmail.com
 
, September 4, 2003 14:59
 
----
 
 
Dan has an end-to-end solution for almost all problems for vim compiling on Windows:
 
 
http://mywebpage.netscape.com/sharppeople/vim/howto/Vim-Compile-Win32-HOWTO/index.html
 
http://mywebpage.netscape.com/sharppeople/vim/howto/Vim-Compile-Win32-HOWTO/index.html
   
maxiangjiang--AT--hotmail.com
 
, September 5, 2003 10:49
 
 
----
 
----
 
Use mingw32 -- gcc for windows. Builds native exe.
Dan is good at compiling many programs under Cygwin, not only the gvim, it is he who tells me how to compile MudOS v22 on cygwin.
 
 
'''Anonymous'''
 
, September 11, 2003 21:12
 
----
 
Use mwing32 -- gcc for windows. Builds native exe.
 
   
 
From http://www.mingw.org/
 
From http://www.mingw.org/
   
MinGW: A collection of freely available and freely distributable Windows specific header files and import libraries combined with GNU toolsets that allow one to produce native Windows programs that do not rely on any 3rd-party DLLs.
+
MinGW: A collection of freely available and freely distributable Windows specific header files and import libraries combined with GNU toolsets that allow one to produce native Windows programs that do not rely on any 3rd-party DLLs.
   
 
mohsin--AT--synplicity.com
 
, September 30, 2003 19:31
 
 
----
 
----
 
Note that the resulting gvim.exe built from cygwin package is "native".
 
Note that the resulting gvim.exe built from cygwin package is "native".
 
 
It has no dependancy on cygwin.dll at all.
 
It has no dependancy on cygwin.dll at all.
   
maxiangjiang--AT--hotmail.com
 
, October 1, 2003 11:54
 
 
----
 
----
The gvim.exe produced does not use cygwin-style paths. :( I've got a lot of cygwin mounts that I would like to use.
+
The gvim.exe produced does not use cygwin-style paths. I've got a lot of cygwin mounts that I would like to use.
  +
:If you want a Vim which understands Cygwin-style paths and runs seamlessly from a Cygwin bash prompt, I recommend the Console Vim build that comes with Cygwin. You will still need a different executable such as the one described above (gvim.exe and/or vim.exe) to run in Windows outside the Cygwin "Unix-like" environment. --[[User:Tonymec|Tonymec]] 16:03, 21 August 2009 (UTC)
 
'''Anonymous'''
 
, October 14, 2003 7:18
 
 
----
 
----
  +
The CVS command "cvs -z3 -d:pserver:anonymous@cvs.vim.org:/cvsroot/vim co vim" no longer works as the domain cvs.vim.org no longer exists. I was looking to this help to give me a more definitive way to compile vim under Cygwin64. The packaged vim in the current distro does not get along with packages under .vim/bundle/vundle (I believe because the version is too old), and finds a lot of things it doesn't understand. Compiling would be great, except that I ran into problems. I compiled it in a way that defaulted into UNIX (probably wrong, but Cygwin behaves as a UNIX-like system, so it was the closest thing I could think of). [[Special:Contributions/216.105.80.60|216.105.80.60]] 03:29, October 2, 2013 (UTC)
<!-- parsed by vimtips.py in 0.435511 seconds-->
 

Latest revision as of 16:55, 2 October 2013

Tip 531 Printable Monobook Previous Next

created 2003 · complexity basic · author maxiangjiang · version 6.0


This tip is deprecated for the following reasons:

The CVS server for Vim is no longer available. Getting the Vim source with Mercurial is now the recommended method, then you will need to compile as detailed in the rest of this tip

This tip is for those who are interested in building gvim.exe on Windows without using MSVC or BCC. The condition is that cygwin is installed.

Following are the three steps (under any shell and any directory).

cvs -z3 -d:pserver:anonymous@cvs.vim.org:/cvsroot/vim co vim
cd vim/src
make -f Make_cyg.mak IME=yes

I have tested under Windows 2000 and have used my own gvim.exe for months without any problem.

Comments[]

Dan Sharp has an end-to-end solution for almost all problems for Vim compiling on Windows: http://mywebpage.netscape.com/sharppeople/vim/howto/Vim-Compile-Win32-HOWTO/index.html


Use mingw32 -- gcc for windows. Builds native exe.

From http://www.mingw.org/

MinGW: A collection of freely available and freely distributable Windows specific header files and import libraries combined with GNU toolsets that allow one to produce native Windows programs that do not rely on any 3rd-party DLLs.


Note that the resulting gvim.exe built from cygwin package is "native". It has no dependancy on cygwin.dll at all.


The gvim.exe produced does not use cygwin-style paths. I've got a lot of cygwin mounts that I would like to use.

If you want a Vim which understands Cygwin-style paths and runs seamlessly from a Cygwin bash prompt, I recommend the Console Vim build that comes with Cygwin. You will still need a different executable such as the one described above (gvim.exe and/or vim.exe) to run in Windows outside the Cygwin "Unix-like" environment. --Tonymec 16:03, 21 August 2009 (UTC)

The CVS command "cvs -z3 -d:pserver:anonymous@cvs.vim.org:/cvsroot/vim co vim" no longer works as the domain cvs.vim.org no longer exists. I was looking to this help to give me a more definitive way to compile vim under Cygwin64. The packaged vim in the current distro does not get along with packages under .vim/bundle/vundle (I believe because the version is too old), and finds a lot of things it doesn't understand. Compiling would be great, except that I ran into problems. I compiled it in a way that defaulted into UNIX (probably wrong, but Cygwin behaves as a UNIX-like system, so it was the closest thing I could think of). 216.105.80.60 03:29, October 2, 2013 (UTC)