On Saturday, August 25, 2012 10:02:30 AM UTC-4, Michael Henry wrote: > All, > > > > I'm interested in compiling Vim for Windows. Ideally, I'd like > > to replicate the "Vim Without Cream" build associated with the > > "Cream" project: > > http://cream.sourceforge.net/ > > > > The Cream FAQ didn't seem to have anything about building from > > source: > > http://cream.sourceforge.net/faq.html > > > > I was hoping to get hold of an installation guide and ideally a > > full build script that would go with it. I had no luck looking > > at the source for Cream (though I'm looking for the "without > > Cream" variant): > > http://sourceforge.net/projects/cream/files/Cream/0.43/ > > > > I'm probably overlooking something obvious; hopefully someone > > can point me in the right direction. > > > > Note that I don't have to have "Vim Without Cream" specifically, > > but it's a nicely done package with a "huge" Vim build and a > > nice installer. It does nearly everything I'd like, but I would > > like to customize certain things about the build (for example, > > I'd like to include the ruby bindings). > > > > I looked for alternatives. There are some tips on the Vim wiki, > > but they seem out of date or not complete enough to replicate a > > huge build from all sources, ideally with an installer as > > well: > > http://vim.wikia.com/wiki/Build_Vim_in_Windows_with_Cygwin > > http://vim.wikia.com/wiki/Build_Vim_in_Windows_with_Visual_Studio > > http://vim.wikia.com/wiki/Build_Python-enabled_Vim_on_Windows_with_MinGW > > > > I took a quick look at Tony's guide: > > http://users.skynet.be/antoine.mechelynck/vim/compile.htm > > > > I didn't try these instructions because Cygwin gcc no longer > > allows the -mno-cygwin flag. > > > > Does anybody have any suggestions? > > > > Thanks, > > Michael Henry
Hi, I have been building vim successfully either vim visual studio or cygwin but including only perl and python, not ruby. For visual studio assuming you have perl in C:\Perl and python in C:\Python27 and that you have the vim source folder somewhere, you just have to go into the folder src type msvc2010.bat and then nmake -f Make_mvc.mak DYNAMIC_PYTHON=yes PYTHON="C:\Python27" PYTHON_VER=27 PERL="C:\Perl" PERL_VER=512 DYNAMIC_PERL=yes FEATURES=HUGE OLE=yes GUI=yes this works for me, building vim with visual studio. For building vim with cygwin, I was also stuck for a while because of that gcc option no longer being valid, but it turns out it is not a big deal. I copied the file Make_cyg.mak to Make_cyg1.mak and then in the file Make_cyg1.mak replaced the lines CC = gcc by CC = i686-pc-mingw32-gcc and INCLUDES += -mno-cygwin by INCLUDES += Then I have this small perl script that I use to compile vim in cygwin %%%%%%%%%%%%%%%%%%%%%%%%%% #!/usr/bin/env perl # compile vim for windows using a cross compiler in cygwing my $python = "PYTHON=/cygdrive/c/Python27 PYTHON_VER=27 DYNAMIC_PYTHON=yes"; my $perl = "PERL=/cygdrive/c/Perl PERL_VER=512 DYNAMIC_PERL=yes"; my $makefile = "Make_cyg1.mak"; my $jflag = "-j5"; my $cmd_vim = "make -B -f $makefile GUI=no $python $perl $jflag vim.exe"; my $cmd_gvim = "make -B -f $makefile GUI=yes $python $perl $jflag gvim.exe"; print "$cmd_vim\n"; system "$cmd_vim"; print "$cmd_gvim\n"; system "$cmd_gvim"; %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% and then I just run this perl script to compile vim in cygwin. I guess maybe the file Make_cyg.mak should be modified in the distribution so that people can use that directly. I would also like to see a guide on how to compile vim 64 bits. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
