Has anyone tried building Vim with Visual C 2015 on Windows yet? I wanted to try building a copy of Vim with Python 3.5 enabled, just to see how well it worked - Python 3.5 uses VC 2015 to build, so I wanted to use the same version for Vim to avoid any weird C runtime clashes that might occur. And just for the interest :-)
There seem to be a number of issues: 1. Win32.mak is no longer available. I see that I can set SDK_INCLUDE_DIR to point to a version of it, but that means installing an old SDK or an old version of Visual Studio, so it's less than ideal... 2. The use of /nodefaultlib causes a load of "unresolved external symbol malloc" and similar issues. The C runtime has been reorganised in VC 2015, which maybe is why this is having issues. Has anyone else tried to build with VC2015, and if so have you worked out how to fix these issues in a reasonable way? Just removing the use of /nodefaultlib *seems* to work, so I could use that for now, but I don't know if that could have problems that I haven't spotted. Thanks, Paul -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
