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?

-- 
-- 
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.

Raspunde prin e-mail lui