search

LegendaryBo / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

Cannot build vim/gvim on Windows 8 with Visual Studio 2015 #357

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have been building gvim/vim from source using Visual Studio 2013 tools with 
no problems. Yesterday, I tried to do the same with Visual Studio 2015 RC 
tools, and for reasons beyond my understanding, the build is failing at link 
stage with a failure to resolve standard C library functions.

As far as I can see, there is nothing in Make_mvc.mak that should not work with 
the new tools (I manually set MSVCVER=12.0 on the command line before invoking 
it).

What steps will reproduce the problem?
1. Open a VS2015 x64 Native Tools Command Prompt
2. set include=%include%;C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.1A\Include for win32.mak
3. set MSVCVER=12.0
4. nmake -f Make_mvc.mak CPU=AMD64 OPTIMIZE=SPACE GETTEXT=no NETBEANS=no 
CSCOPE=no DIRECTX=yes GUI=yes

What is the expected output? What do you see instead?

I expect gvim.exe to be created. Instead, I get link errors referring to 
standard C functions and others:

winclip.obj : error LNK2001: unresolved external symbol memcpy
screen.obj : error LNK2001: unresolved external symbol memmove
misc1.obj : error LNK2001: unresolved external symbol realloc

etc etc etc

What version of the product are you using? On what operating system?

Vim 7.4.712, Windows 8.1 Pro

Please provide any additional information below.

I also created a question on Stackoverflow for this issue.

http://stackoverflow.com/questions/29986585/why-am-i-not-able-to-build-vim-with-
visual-studio-2015-rc-command-line-tools

My hope was to figure out what ever needed adding to Make_mvc.mak for this 
build, and contribute a patch, but, alas I seem to have hit a wall.

Thank you.

-- Sinan

Original issue reported on code.google.com by sinan.u...@gmail.com on 1 May 2015 at 3:12

GoogleCodeExporter commented 9 years ago 
Can you check, if this patch works for you?
https://groups.google.com/d/msg/vim_dev/YmhhsZKPHNY/wlOGga8mjdcJ

Original comment by chrisbr...@googlemail.com on 1 May 2015 at 7:59

GoogleCodeExporter commented 9 years ago 
Yes ... That did the trick!

I do not know how I missed that when I was searching. Thank you very much for 
pointing me to it.

-- Sinan

Original comment by sinan.u...@gmail.com on 1 May 2015 at 8:43

GoogleCodeExporter commented 9 years ago 
fixed by 7.4.720

Original comment by chrisbr...@googlemail.com on 4 May 2015 at 4:59