Obsolete tip
This tip has been merged into another tip.
See VimTip1578 for the current tip.
Please do not edit this tip, and do not edit the discussion page.
If anything needs to be improved, please fix VimTip1578.
created March 12, 2001 · complexity basic · author benji · version 5.7
Windows binaries of vim 5.7 are available with perl and python support turned on at:
Comments
If you have VisualC++ 6.0, then you are well recommended to use the really cool delay loading feature to delay-load the perl DLLs. The advantage of this is that if your machine doesn't have a suitable perl DLL available, then gvim will still run fine (so long as you don't try to use any perl inside the vim session of course). Oh, and since the Perl DLL uses the C runtime in DLL form (msvcrt.dll), then gvim/vim should also do this (that's "/MD" in uSoft speak). In Makefile,w32 I use:
CFLAGS = $(CFLAGS) -DNDEBUG /Ox /G6 /Ob1 /Os /MD /Gy PERL_LIB = /DelayLoad:perl56.dll $(PERL)\Lib\Core\perl56.lib DelayImp.lib
(i.e., the link line has "/DelayLoad:perl56.dll" added. Some stub code is required to support delay loading, and uSoft supply this in DelayImp.lib). I also find that I need to append "/I $(PERL)\Lib\MSWin32-x86\Core" to PERL_INC too.
http://www.cs.fhm.edu/~ifw00065/vim/
The current CVS version of Vim (post 6.0.158) compiled for Windows with the Python interface enabled (Python 2.2) plus VisVim and OLE. IOW, everything like the standard 6.0.0 release from the Vim folks, just newer and with Python 2.2 support. Using the latest NSIS installer with bip2 compression, it's also much smaller than the original. It's only 2.3 megs :-)