2008/7/11 Will Rogers <[EMAIL PROTECTED]>: > On Jul 9, 3:47 am, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > The changes for 64 bit support were included in the source code. I'm > > only building the 32 bit version, because it runs everywhere. > > The problem with running 32-bit Vim on 64-bit Windows is the shell > extensions do not work. That is, the installer fails to add the "Edit > with Vim" context menu entries. I'm guessing you are already aware of > this, but I want to say it again, because that context menu entry is > my favorite feature of Vim on Windows. >
There's no easy workaround in the Win32 version. It's not possible to load a 32-bit DLL into a 64-bit process -- though it's certainly possible to load a 32-bit DLL into a 32-bit process running on Win64, which is why the 32-bit vim.exe works. The Explorer is a 64-bit process, of course. An official 64-bit Windows installer would be very nice and helpful. > I just looked and discovered that NSIS now claims to support x64 installations. However, I have yet to successfully build the NSIS installer for Win32, though I haven't tried recently. I did find it fairly straightforward to build my own using VC9, > though, so kudos for the excellent build support. If official 64-bit > builds are *not* forthcoming (which I'm guessing they aren't, given > Bram's answer I'm quoting), I'd appreciate it if someone would provide > a little more "what to do after you've built it" documentation, or > perhaps an updated, working Nullsoft installer? Specifically, these > are the things I found confusing when "rolling my own": > Some hints at http://www.georgevreilly.com/vim/. Basically, To install Vim, first download vim72a-019-x64.zip<http://www.georgevreilly.com/vim/vim72a-019-x64.zip>. This 18MB file contains all the files you need for a full installation, including the latest Vim runtime. Unzip the zipfile into a directory whose name ends in vim, such as C:\Program Files\Vim, D:\vim, or C:\mytools\vim. This will create a vim72asubdirectory, containing all the files. Start a cmd.exe window, cd ...\vim\vim72a, then run install, the command-line installer. This will offer you a series of choices. You can probably just type d to "do it". On Vista, you must run the cmd window as an Administrator. To uninstall, use uninstall.exe in the same directory. I've attached mkdist.bat, which I use to assemble the zipfile -- renamed to get around restrictions on sending executables. 1. What does OLE support do, and is it even relevant for modern > Windows? > :help if_ole.txt, though you probably won't find it very enlightening. Something to do with VisVim, which I don't think works on any version of Visual Studio after VS98. I've never knowingly used the OLE interface, just made it build cleanly on Win64. 2. After I've built vim, which files do I need? There are several EXEs > and DLLs produced in a couple different subdirectories of src/, but > the INSTALL* documentation files don't explain what to do with them in > the absence of UNIX-style "make install". For example, what is xxd.exe > and do I need it? > See mkdist.bat, attached. 3. Is nsis/gvim.nsi in the repository supposed to work? It seems > stale. > Bram says so. -- /George V. Reilly [EMAIL PROTECTED] http://www.georgevreilly.com/blog http://blogs.cozi.com/tech --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
mkdist.b_t
Description: Binary data
