On Mon, Jul 2, 2012 at 6:33 AM, Chris Sutcliffe <[email protected]> wrote: > On 1 July 2012 16:23, Bram Moolenaar wrote: >> Charles wrote: >>> Using Visual C++ 2010 in XP and WINVER=0x500, find / replace dialogs >>> do not work (the commands just fail silently). >>> >>> As an alternative, we can load kernel32.dll and bind the memory >>> address of MemoryStatusEx. If it isn't found, then fallback to >>> MemoryStatus, thus eliminating the requirement of changing WINVER. >> >> Setting WINVER to 0x0500 is needed at compile time. The idea was to set >> the default in Make_ming.mak and Make_cyg.mak, thus Visual C++ is >> unaffected. > > I've built a native Windows gvim using the MinGW and mingw-w64 > toolchains under Cygwin using the following commands: > > MinGW: > make -f Make_ming.mak CROSS=yes CROSS_COMPILE=i686-pc-mingw32- WINVER=0x0500 > > mingw-w64: > make -f Make_ming.mak CROSS=yes CROSS_COMPILE=i686-w64-mingw32- WINVER=0x0500 > > in both cases gvim worked as expected (including the find and replace > dialogues). > > So I think setting WINVER to 0x0500 in Make_ming.mak is safe.
Alternatively, this condition in the patch if (g_PlatformId != VER_PLATFORM_WIN32_NT) can be replaced with if (WINVER <= 0x400) which is more correct since NT does not have MemoryStatusEx. By the way, assuming most people do not compile gvim themselves, what WINVER value will be used to compile gvim windows binary distribution? -- 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
