Re: 64-bit support for Windows (Vista)
On Tuesday, August 28, 2012 1:05:01 AM UTC-4, Sergey Khorev wrote: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS ... advapi32.lib shell32.lib /machine:i386 /no Ok, the problem is in /machine:i386 which should be AMD64 for x64 builds. Either something is wrong with your environment or Make_mvc.mak failed to detect the target architecture properly. Can you check what commands below show before and after you source vcvarsx86_amd64.bat? set PROCESSOR_ARCHITECTURE set ASSEMBLY_ARCHITECTURE set CPU This might be obvious but I just figured it out now. The easiest way of solving this issue is simply to pass the correct option in the command line. In my case: nmake -f Make_mvc.mak CPU=AMD64 other_options -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
Next steps is to make it work with perl and python and I will be using this version :) Cool. Also it would be interesting to know why the makefile chose i386 as the target platform. Unfortunately I cannot suggest anything more sensible than putting echo ASSEMBLY_ARCHITECTURE: $(ASSEMBLY_ARCHITECTURE) CPU: $(CPU) PROCESSOR_ARCHITECTURE: $(PROCESSOR_ARCHITECTURE) where it works with these env vars. Also compiled successfully with python and perl.. Additionally the other thing I had to compile was ctags, the version that used to work with the 32 bit version doesn't seem to be recognized by the 64 bit version. -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
This is already a quite old thread but I can't find easily any instruction on how to compile vim for 64 bit windows. I am using windows 7. I tried the following: first I call c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat to set up the vars to 64 bit. Then I try to compile just with nmake -f Make_mvc.mak GUI=yes and all the files seem to compile fine until it reaches the link step where the error is: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjG/ /Ox /GL -DNDEBUG /Zl /MT -DFEAT_GUI_W32 -DDYNAMIC _ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjG/ /Zi version.c version.c link /RELEASE /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe .\ObjG\blowfish.obj .\Obj G\buffer.obj .\ObjG\charset.obj .\ObjG\diff.obj .\ObjG\digraph.obj .\ObjG\edit.obj .\ObjG\eval.ob j .\ObjG\ex_cmds.obj .\ObjG\ex_cmds2.obj .\ObjG\ex_docmd.obj .\ObjG\ex_eval.obj .\ObjG\ex_getln.o bj .\ObjG\fileio.obj .\ObjG\fold.obj .\ObjG\getchar.obj .\ObjG\hardcopy.obj .\ObjG\hashtab.obj . \ObjG\main.obj .\ObjG\mark.obj .\ObjG\mbyte.obj .\ObjG\memfile.obj .\ObjG\memline.obj .\ObjG\menu .obj .\ObjG\message.obj .\ObjG\misc1.obj .\ObjG\misc2.obj .\ObjG\move.obj .\ObjG\normal.obj .\Ob jG\ops.obj .\ObjG\option.obj .\ObjG\os_mswin.obj .\ObjG\os_win32.obj .\ObjG\pathdef.obj .\ObjG\po pupmnu.obj .\ObjG\quickfix.obj .\ObjG\regexp.obj .\ObjG\screen.obj .\ObjG\search.obj .\ObjG\sha25 6.obj .\ObjG\spell.obj .\ObjG\syntax.obj .\ObjG\tag.obj .\ObjG\term.obj .\ObjG\ui.obj .\ObjG\und o.obj .\ObjG\window.obj .\ObjG\vim.res .\ObjG\gui.obj .\ObjG\gui_beval.obj .\ObjG\gui_w32.obj .\O bjG\os_w32exe.obj.\ObjG/if_cscope.obj .\ObjG/netbeans.obj .\ObjG\version.obj oldnames.li b kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /node faultlib gdi32.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386 /no defaultlib libcmt.lib user32.lib WSock32.lib /PDB:gvim.pdb -debug .\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine typ e 'X86' NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\x86_amd64\link .EXE' : return code '0x458' Stop. Any ideas on how to compile this? I guess this would be nice thing to have for the next release. Thanks, Jorge -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
On Mon, Aug 27, 2012 at 9:28 AM, skeept ske...@gmail.com wrote: This is already a quite old thread but I can't find easily any instruction on how to compile vim for 64 bit windows. I am using windows 7. I tried the following: first I call c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat to set up the vars to 64 bit. Then I try to compile just with nmake -f Make_mvc.mak GUI=yes and all the files seem to compile fine until it reaches the link step where the error is: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjG/ /Ox /GL -DNDEBUG /Zl /MT -DFEAT_GUI_W32 -DDYNAMIC _ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjG/ /Zi version.c version.c link /RELEASE /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe .\ObjG\blowfish.obj .\Obj G\buffer.obj .\ObjG\charset.obj .\ObjG\diff.obj .\ObjG\digraph.obj .\ObjG\edit.obj .\ObjG\eval.ob j .\ObjG\ex_cmds.obj .\ObjG\ex_cmds2.obj .\ObjG\ex_docmd.obj .\ObjG\ex_eval.obj .\ObjG\ex_getln.o bj .\ObjG\fileio.obj .\ObjG\fold.obj .\ObjG\getchar.obj .\ObjG\hardcopy.obj .\ObjG\hashtab.obj . \ObjG\main.obj .\ObjG\mark.obj .\ObjG\mbyte.obj .\ObjG\memfile.obj .\ObjG\memline.obj .\ObjG\menu .obj .\ObjG\message.obj .\ObjG\misc1.obj .\ObjG\misc2.obj .\ObjG\move.obj .\ObjG\normal.obj .\Ob jG\ops.obj .\ObjG\option.obj .\ObjG\os_mswin.obj .\ObjG\os_win32.obj .\ObjG\pathdef.obj .\ObjG\po pupmnu.obj .\ObjG\quickfix.obj .\ObjG\regexp.obj .\ObjG\screen.obj .\ObjG\search.obj .\ObjG\sha25 6.obj .\ObjG\spell.obj .\ObjG\syntax.obj .\ObjG\tag.obj .\ObjG\term.obj .\ObjG\ui.obj .\ObjG\und o.obj .\ObjG\window.obj .\ObjG\vim.res .\ObjG\gui.obj .\ObjG\gui_beval.obj .\ObjG\gui_w32.obj .\O bjG\os_w32exe.obj.\ObjG/if_cscope.obj .\ObjG/netbeans.obj .\ObjG\version.obj oldnames.li b kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /node faultlib gdi32.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386 /no defaultlib libcmt.lib user32.lib WSock32.lib /PDB:gvim.pdb -debug .\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine typ e 'X86' NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\x86_amd64\link .EXE' : return code '0x458' Stop. Any ideas on how to compile this? I guess this would be nice thing to have for the next release. Thanks, Jorge There are some old and sadly neglected batch files at http://code.google.com/p/vim-win3264/downloads/list that will help in building a native Win64 build of Vim. I don't use Windows much anymore and when I do, I run the Win32 binaries by default on Win64, for the reasons elucidated at http://code.google.com/p/vim-win3264/ -- /George V. Reilly geo...@reilly.org Twitter: @georgevreilly http://www.georgevreilly.com/blog http://blogs.cozi.com/tech -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
.\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine typ e 'X86' NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\x86_amd64\link .EXE' : return code '0x458' Apparently the linker tries using x86 binaries. The simplest solution would be delete ObjG directory and build from scratch. -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
On Tue, Aug 28, 2012 at 12:11 AM, Sergey Khorev sergey.kho...@gmail.com wrote: .\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine typ e 'X86' NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\x86_amd64\link .EXE' : return code '0x458' Apparently the linker tries using x86 binaries. The simplest solution would be delete ObjG directory and build from scratch. Thanks, I just tried that but the result is exactly the same. It compiles all the files correctly but linking gives the same error as before. Jorge -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
Apparently the linker tries using x86 binaries. The simplest solution would be delete ObjG directory and build from scratch. Thanks, I just tried that but the result is exactly the same. It compiles all the files correctly but linking gives the same error as before. Can you remove ObjG again and paste here the full build log? -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
Can you remove ObjG again and paste here the full build log? Sure, here it goes: C:\htemp\vim\src c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat Setting environment for using Microsoft Visual Studio 2010 x64 cross tools. C:\htemp\vim\srcnmake -f Make_mvc.mak GUI=yes gvim.exe Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. if not exist .\ObjG/nul mkdir .\ObjG creating .\ObjG\pathdef.c cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjG/ /Ox /GL -DNDEBUG /Zl /MT -DFEAT_GUI_W32 -DDYNAMIC _ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjG/ /Zi .\ObjG\pathdef.c pathdef.c rc /l 0x409 /Fo.\ObjG/vim.res /r -DWIN32 -D_WIN32 -DWINVER=0x0500 -DNDEBUG -DFEAT_GUI_W32 vim .rc Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 Copyright (C) Microsoft Corporation. All rights reserved. cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjG/ /Ox /GL -DNDEBUG /Zl /MT -DFEAT_GUI_W32 -DDYNAMIC _ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjG/ /Zi blowfish.c buffer.c charset.c diff.c digraph.c edit .c eval.c ex_cmds.c ex_cmds2.c ex_docmd.c ex_eval.c ex_getln.c fileio.c fold.c getchar.c hardcopy.c ha shtab.c main.c mark.c mbyte.c memfile.c memline.c menu.c message.c misc1.c misc2.c move.c normal.c ops .c option.c os_mswin.c os_win32.c popupmnu.c quickfix.c regexp.c screen.c search.c sha256.c spell.c sy ntax.c tag.c term.c ui.c undo.c window.c gui.c gui_beval.c gui_w32.c os_w32exe.c if_cscope.c netbeans. c blowfish.c buffer.c charset.c diff.c digraph.c edit.c eval.c ex_cmds.c ex_cmds2.c ex_docmd.c ex_eval.c ex_getln.c fileio.c fold.c getchar.c hardcopy.c hashtab.c main.c mark.c mbyte.c Compiling... memfile.c memline.c menu.c message.c misc1.c misc2.c move.c normal.c ops.c option.c os_mswin.c os_win32.c popupmnu.c quickfix.c regexp.c screen.c search.c sha256.c spell.c syntax.c Compiling... tag.c term.c ui.c undo.c window.c gui.c gui_beval.c gui_w32.c os_w32exe.c if_cscope.c netbeans.c cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjG/ /Ox /GL -DNDEBUG /Zl /MT -DFEAT_GUI_W32 -DDYNAMIC _ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjG/ /Zi version.c version.c link /RELEASE /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe .\ObjG\blowfish.obj .\Obj G\buffer.obj .\ObjG\charset.obj .\ObjG\diff.obj .\ObjG\digraph.obj .\ObjG\edit.obj .\ObjG\eval.ob j .\ObjG\ex_cmds.obj .\ObjG\ex_cmds2.obj .\ObjG\ex_docmd.obj .\ObjG\ex_eval.obj .\ObjG\ex_getln.o bj .\ObjG\fileio.obj .\ObjG\fold.obj .\ObjG\getchar.obj .\ObjG\hardcopy.obj .\ObjG\hashtab.obj . \ObjG\main.obj .\ObjG\mark.obj .\ObjG\mbyte.obj .\ObjG\memfile.obj .\ObjG\memline.obj .\ObjG\menu .obj .\ObjG\message.obj .\ObjG\misc1.obj .\ObjG\misc2.obj .\ObjG\move.obj .\ObjG\normal.obj .\Ob jG\ops.obj .\ObjG\option.obj .\ObjG\os_mswin.obj .\ObjG\os_win32.obj .\ObjG\pathdef.obj .\ObjG\po pupmnu.obj .\ObjG\quickfix.obj .\ObjG\regexp.obj .\ObjG\screen.obj .\ObjG\search.obj .\ObjG\sha25 6.obj .\ObjG\spell.obj .\ObjG\syntax.obj .\ObjG\tag.obj .\ObjG\term.obj .\ObjG\ui.obj .\ObjG\und o.obj .\ObjG\window.obj .\ObjG\vim.res .\ObjG\gui.obj .\ObjG\gui_beval.obj .\ObjG\gui_w32.obj .\O bjG\os_w32exe.obj.\ObjG/if_cscope.obj .\ObjG/netbeans.obj .\ObjG\version.obj oldnames.li b kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /node faultlib gdi32.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386 /no defaultlib libcmt.lib user32.lib WSock32.lib /PDB:gvim.pdb -debug .\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine typ e 'X86' NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\x86_amd64\link .EXE' : return code '0x458' Stop. -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
link /RELEASE /nologo /subsystem:windows /LTCG:STATUS ... advapi32.lib shell32.lib /machine:i386 /no Ok, the problem is in /machine:i386 which should be AMD64 for x64 builds. Either something is wrong with your environment or Make_mvc.mak failed to detect the target architecture properly. Can you check what commands below show before and after you source vcvarsx86_amd64.bat? set PROCESSOR_ARCHITECTURE set ASSEMBLY_ARCHITECTURE set CPU -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
On Tue, Aug 28, 2012 at 1:04 AM, Sergey Khorev sergey.kho...@gmail.com wrote: set PROCESSOR_ARCHITECTURE set ASSEMBLY_ARCHITECTURE set CPU Before and after setting the vars the result is the same: C:\htemp\vim\srcset PROCESSOR_ARCHITECTURE PROCESSOR_ARCHITECTURE=AMD64 C:\htemp\vim\src set ASSEMBLY_ARCHITECTURE Environment variable ASSEMBLY_ARCHITECTURE not defined C:\htemp\vim\src set CPU Environment variable CPU not defined -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
... advapi32.lib shell32.lib /machine:i386 /no Ok, the problem is in /machine:i386 which should be AMD64 for x64 builds. Either something is wrong with your environment or Make_mvc.mak failed to detect the target architecture properly. Thanks, you were right. I copied the line doing the final link and replaced i386 by AMD64 and gvim build successfully! Next steps is to make it work with perl and python and I will be using this version :) -- You received this message from the vim_dev 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
Re: 64-bit support for Windows (Vista)
Will Rogers wrote:
3. Is nsis/gvim.nsi in the repository supposed to work?
Bram says so.
First, let me say that it's funny that the instructions for building
the Windows installer include a step that says, You may have to do
this on UNIX.
The NSIS script does not appear to work out of the box, unless I
missed a step. I had to go through and make a bunch of minor edits,
e.g.
!define VIMRT .. - !define VIMRT ..\runtime
:%s/installw32/install/g
:%s/uninstalw32/uninstal/g
${VIMSRC}\xxd.exe - ${VIMSRC}\xxd\xxd.exe
${VIMRT}\README.txt - ..\README.txt
etc.
Eventually, I gave up. Is there something I should have done
differently to make it Just Work(tm)?
It sounds like you have unpacked the three source archives on
MS-Windows. The NSIS script is made to work with the MS-Windows source
archive. And after following the instructions in the Makefile in the
top directory, this moves some executables around.
Yes, this is a bit clumsy. But for me it's the only reliable way to
produce a release with all the different executables. There are four of
five different install.exe binaries produced, for example.
--
I noticed my daughter's Disney-net password on a sticky note:
MickeyMinnieGoofyPluto. I asked her why it was so long.
Because they say it has to have at least four characters.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: 64-bit support for Windows (Vista)
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. An official 64-bit Windows installer would be very nice and helpful. 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: 1. What does OLE support do, and is it even relevant for modern Windows? 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? 3. Is nsis/gvim.nsi in the repository supposed to work? It seems stale. Thanks, -- Will --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: 64-bit support for Windows (Vista)
On 11/07/08 16:41, Will Rogers wrote: [...] For example, what is xxd.exe and do I need it? [...] xxd is a program to convert binary to hex and vice-versa. It is useful to hex-edit binary files. See :help using-xxd. Best regards, Tony. -- flowchart, n. v.: [From flow to ripple down in rich profusion, as hair + chart a cryptic hidden-treasure map designed to mislead the uninitiated.] 1. n. The solution, if any, to a class of Mascheroni construction problems in which given algorithms require geometrical representation using only the 35 basic ideograms of the ANSI template. 2. n. Neronic doodling while the system burns. 3. n. A low-cost substitute for wallpaper. 4. n. The innumerate misleading the illiterate. A thousand pictures is worth ten lines of code. -- The Programmer's Little Red Vade Mecum, Mao Tse T'umps. 5. v.intrans. To produce flowcharts with no particular object in mind. 6. v.trans. To obfuscate (a problem) with esoteric cartoons. -- Stan Kelly-Bootle, The Devil's DP Dictionary --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: 64-bit support for Windows (Vista)
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.ziphttp://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
Re: 64-bit support for Windows (Vista)
Will Rogers wrote: 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. An official 64-bit Windows installer would be very nice and helpful. George mentioned he would have a look at it. 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: 1. What does OLE support do, and is it even relevant for modern Windows? Yes, it's used for some features. 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? Yeah, there should be a make install equivalent. Unfortunately, MS hasn't made this easy for us. Running the install.exe should work. 3. Is nsis/gvim.nsi in the repository supposed to work? It seems stale. It's used to build the self-installing executable. It should have: !define VER_MAJOR 7 !define VER_MINOR 2a -- hundred-and-one symptoms of being an internet addict: 211. Your husband leaves you...taking the computer with him and you call him crying, and beg him to bring the computer back. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: 64-bit support for Windows (Vista)
Thanks, Tony, George, and Bram, for the informative replies. I have a
little more specific feedback, which I've provided by quoting George's
message below. I do understand if improving the build documentation
isn't a priority, because obvious the important people (Bram) already
know how to do it.
On Jul 11, 2:42 pm, George V. Reilly [EMAIL PROTECTED] wrote:
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.
Yes, which is why I said an official 64-bit version would be nice. ;)
Some hints athttp://www.georgevreilly.com/vim/. Basically,
[snip stuff about extracting, running install.exe, etc.]
These parts are easy enough to figure out. It's figuring out how to
assemble the zip file after building that's confusing.
I've attached mkdist.bat, which I use to assemble the zipfile
Thanks for this. A few words about how to do this by hand in
INSTALLpc.txt would be greatly appreciated. All it would need is a
list of the files you need to copy out of the source tree and a few
words about how to arrange them for use.
:help if_ole.txt, though you probably won't find it very enlightening.
Actually, that was fairly enlightening. Again, a few words in
INSTALLpc.txt saying something to the effect of If you want to be
able to automate Vim from another program or script, enable OLE would
be helpful. Currently, it does not provide any information that would
help the OLE-clueless (e.g. me) decide whether they need it or not.
Incidentally, isn't VisVim somewhat obsolete?
3. Is nsis/gvim.nsi in the repository supposed to work?
Bram says so.
First, let me say that it's funny that the instructions for building
the Windows installer include a step that says, You may have to do
this on UNIX.
The NSIS script does not appear to work out of the box, unless I
missed a step. I had to go through and make a bunch of minor edits,
e.g.
!define VIMRT .. - !define VIMRT ..\runtime
:%s/installw32/install/g
:%s/uninstalw32/uninstal/g
${VIMSRC}\xxd.exe - ${VIMSRC}\xxd\xxd.exe
${VIMRT}\README.txt - ..\README.txt
etc.
Eventually, I gave up. Is there something I should have done
differently to make it Just Work(tm)?
-- Will
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: 64-bit support for Windows (Vista)
2008/7/11 Will Rogers [EMAIL PROTECTED]:
I've attached mkdist.bat, which I use to assemble the zipfile
Thanks for this. A few words about how to do this by hand in
INSTALLpc.txt would be greatly appreciated. All it would need is a
list of the files you need to copy out of the source tree and a few
words about how to arrange them for use.
Agreed.
:help if_ole.txt, though you probably won't find it very enlightening.
Actually, that was fairly enlightening. Again, a few words in
INSTALLpc.txt saying something to the effect of If you want to be
able to automate Vim from another program or script, enable OLE would
be helpful. Currently, it does not provide any information that would
help the OLE-clueless (e.g. me) decide whether they need it or not.
Incidentally, isn't VisVim somewhat obsolete?
Judging by http://www.unwoundstack.com/?page_id=16, yes. VisVim works only
with DevStudio 5 or 6, not Visual Studio.NET 2002 onwards. The same article
indicates that with a bit of work, it's possible to write an add-in that
will work in VS200[2358].
3. Is nsis/gvim.nsi in the repository supposed to work?
Bram says so.
First, let me say that it's funny that the instructions for building
the Windows installer include a step that says, You may have to do
this on UNIX.
The NSIS script does not appear to work out of the box, unless I
missed a step. I had to go through and make a bunch of minor edits,
e.g.
!define VIMRT .. - !define VIMRT ..\runtime
:%s/installw32/install/g
:%s/uninstalw32/uninstal/g
${VIMSRC}\xxd.exe - ${VIMSRC}\xxd\xxd.exe
${VIMRT}\README.txt - ..\README.txt
etc.
Eventually, I gave up. Is there something I should have done
differently to make it Just Work(tm)?
I ran into the same problems when I tried many months ago. Bram says that
it's all set up by the Makefile in the root directory, but I think you'll
need a bunch of Unix-y tools to drive the process. I don't know whether
Cygwin, GnuWin32, or MinGW toolchains will suffice.
--
/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
-~--~~~~--~~--~--~---
Re: 64-bit support for Windows (Vista)
Brian Mathis wrote: With 7.2a now out, I didn't see any mention of support for 64-bit Windows. Vista (whatever you feel about it) really is the gateway to 64-bit on the Windows platform. This is my plea that 7.2 supports 64- bit Windows out of the box. All of the work is already done. There is a site here: http://georgevreilly.com/vim/ that already works. I sure would like to have an official version though. The changes for 64 bit support were included in the source code. I'm only building the 32 bit version, because it runs everywhere. Hopefully also on Windows 98 and ME after the next build. If you want the 64 bit version you either need to build yourself, or wait for someone (possibly George Reilly) to make a 64 bit version available. Maybe some day we'll include the 64 bit version in the installer, and pick the right executable when doing the install. -- Some of the well know MS-Windows errors: ESLEEP Operator fell asleep ENOERR No error yet EDOLLAR OS too expensive EWINDOWSMS-Windows loaded, system in danger /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
64-bit support for Windows (Vista)
Hello, With 7.2a now out, I didn't see any mention of support for 64-bit Windows. Vista (whatever you feel about it) really is the gateway to 64-bit on the Windows platform. This is my plea that 7.2 supports 64- bit Windows out of the box. All of the work is already done. There is a site here: http://georgevreilly.com/vim/ that already works. I sure would like to have an official version though. Thanks. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
