Hi, 2015/7/23 Thu 8:54:21 UTC+9 Raymond Ko wrote: > Hello all, > > When I was running my own build script, I got the following error during link > stage: > > unresolved external symbol __iob_func referenced in function OpenReadFile > > With some investigation, I found if I set XPM=no, then it would link > successfully. Since I don't think I use XPM images for signs anyways, it > shouldn't affect me. > > Looking at the root cause, I found that the XPM library for Windows was > distributed as *.lib and *.a static library files. > > Googling didn't reveal too much information about the cause of this, but it > seems to be a Visual C runtime mismatch issue? Vim is compiled with cl.exe > /MT (multithreaded runtime, the default), but I think XPM is compiled with > something else, and is causing a conflict. > > Would anyone else be able to confirm? And if so, would it be possible to > bundle the source instead and always compile it instead of distributing > binaries, or is there a reason binaries are needed?
VS2015 has new CRT (Universal CRT). This is the cause of the error. See: http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx If you want to build libXpm by yourself, using koron's win32 port might be easy. See: https://github.com/koron/libXpm-win32 Regards, Ken Takata -- -- 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.
