VS2005 linking errors with FEATURES=TINY GUI=yes OLE=yes
Hi developers If I compile vim on Windows XP with Microsoft Visual Studio 2005 Express Edition on the command line with nmake -f Make_mvc.mak DEBUG=yes FEATURES=TINY GUI=yes OLE=yes I get the errors: ex_cmds2.obj : error LNK2019: unresolved external symbol _get_locale_val referenced in function _get_mess_env os_mswin.obj : error LNK2019: unresolved external symbol _gui_mch_dialog referenced in function _display_errors Is this a bug or isn't this configuration supported for certain reasons? Thanks for any replies! Best regards Mathias
Patch: nmake DEBUG=yes FEATURES=NORMAL GUI=yes OLE=yes fails
Patch 7.0.mswin Problem:On Windows, when gvim is built by the command nmake -f Make_mvc.mak DEBUG=yes FEATURES=NORMAL GUI=yes OLE=yes then the linker will issue the error message if_ole.obj : error LNK2019:i unresolved external symbol _MultiByteToWideChar_alloc referenced in function public: virtual long __stdcall CVim::Eval(wchar_t *,wchar_t * *) Solution: Include this function into the built also when OLE is enabled. Files: src/mswin.c *** ..\vim-7.0.000\src\os_mswin.c 2006-05-07 16:13:03.0 +0200 --- src\os_mswin.c 2006-06-04 17:38:32.981234300 +0200 *** *** 957,962 --- 957,966 return outlen; } + #endif /* FEAT_MBYTE */ + + #if defined(FEAT_MBYTE) || defined(FEAT_OLE) || defined(PROTO) + /* * Call MultiByteToWideChar() and allocate memory for the result. * Returns the result in *out[*outlen] with an extra zero appended. *** *** 977,982 --- 981,990 } } + #endif /* FEAT_MBYTE || FEAT_OLE */ + + #if defined(FEAT_MBYTE) || defined(PROTO) + /* * Call WideCharToMultiByte() and allocate memory for the result. * Returns the result in *out[*outlen] with an extra NUL appended. -- Thanks a lot for the VIM Editor Greetings Mathias
Re: VS2005 linking errors with FEATURES=TINY GUI=yes OLE=yes
Mathias Michaelis wrote: Hi developers If I compile vim on Windows XP with Microsoft Visual Studio 2005 Express Edition on the command line with nmake -f Make_mvc.mak DEBUG=yes FEATURES=TINY GUI=yes OLE=yes I get the errors: ex_cmds2.obj : error LNK2019: unresolved external symbol _get_locale_val referenced in function _get_mess_env os_mswin.obj : error LNK2019: unresolved external symbol _gui_mch_dialog referenced in function _display_errors Is this a bug or isn't this configuration supported for certain reasons? Thanks for any replies! Best regards Mathias I guess it's a bug; but Tiny features means barest bones, without arithmetic evaluation and without syntax highlighting. I don't recommend it. On Windows the default is Normal features and I recommend Big or Huge, especially for a debug version. On Unix-like systems, on some systems such as RedHat or SuSE there may be up to three different featuresets of a single version and patchlevel, as follows; any or all of them may be installed on a given machine: - vi, which is actually Vim with Tiny features and no GUI, placed in a directory that will always be mounted, for use in single-user-without-X11 system repair mode (packages vim-common and vim-minimal) - vim with Big features but no GUI, for use in Console mode, in /dev/tty or possibly in an xterm (vim-common and vim-enhanced) - gvim with Big or Huge features and GUI, for use in X11 (vim-common and vim-x11). Best regards, Tony.
Re: VS2005 linking errors with FEATURES=TINY GUI=yes OLE=yes
Hi Mathias, On 6/4/06, Mathias Michaelis [EMAIL PROTECTED] wrote: Hi developers If I compile vim on Windows XP with Microsoft Visual Studio 2005 Express Edition on the command line with nmake -f Make_mvc.mak DEBUG=yes FEATURES=TINY GUI=yes OLE=yes I get the errors: ex_cmds2.obj : error LNK2019: unresolved external symbol _get_locale_val referenced in function _get_mess_env os_mswin.obj : error LNK2019: unresolved external symbol _gui_mch_dialog referenced in function _display_errors Is this a bug or isn't this configuration supported for certain reasons? You should be able to compile Vim with the tiny feature set. I guess some more checks needs to be added to the feature.h file. - Yegappan
