You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
sinan.u...@gmail.com
on 1 May 2015 at 3:12The text was updated successfully, but these errors were encountered: