Mike Williams wrote: > Hi, > > I am trying to build a terminal version of VIM that includes terminal > support. My build line run in the src directory are: > > nmake -nologo -f make_mvc.mak TERMINAL=yes FEATURES=BIG > > The final link fails with: > > vterm_unicode.obj : error LNK2001: unresolved external symbol utf_uint2cells > vterm_unicode.obj : error LNK2001: unresolved external symbol > utf_iscomposing_uint > vim.exe : fatal error LNK1120: 2 unresolved externals > > The invoked compilation command is: > > cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE > -DFEAT_TERMINAL -DFEAT_SOUND -DWINVER=0x0501 > -D_WIN32_WINNT=0x0501 /source-charset:utf-8 /MP -DHAVE_STDINT_H /Ox > /GL -DNDEBUG /Zl /MT /D_CRT_SECURE_NO_DEPRECATE > /D_CRT_NONSTDC_NO_DEPRECATE -DFEAT_MBYTE_IME -DDYNAMIC_IME > -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON > -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_BIG /Fd.\ObjCYAMD64/ /Zi > /Fo.\ObjCYAMD64/ ... > > The missing symbols are from mbyte.c and checking there I can see they > are compiled in if FEAT_TERMINAL is defined, which it appears to be. > And yes mbyte.c appears in the list of files to compile and compiled.
Strange, it can't see why it happens. Maybe make_mvc.mak is missing a dependency and it's linking with an old object file as a result? Can you do do a clean build to make sure that this is not the issue? Regards Dominique -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_jKd3G2gm3F%3DHKNQMJ2LOVFRhA%3DTs37ZU1GWscQXHxupQ%40mail.gmail.com.
