On 15/03/09 22:21, Bram Moolenaar wrote: > > > Markus Heidelberg wrote: > >> You should not need to do *any* editing of any files to get vim compiled >> this >> way. If, for some reason, you want the console-mode-only version of vim >> (this >> -is NOT recommended on Win32, especially on '95/'98!!!), you need only change >> -the 'gvim.exe' to 'vim.exe' in the 'make' commands given above. >> +is NOT recommended on Win32, especially on '95/'98!!!), you need to type: >> + >> + make -f Make_ming.mak GUI=no vim.exe >> > > Thanks, I'll include it. >
Hm; at first I thought this was too limiting, but then I checked the INSTALLpc.txt and saw that this paragraph is part of the section about compiling with the MinGW compiler. However, personally, I don't agree with the recommendation not to compile the console version for W32 -- not even the recommendation not to do it for W98. When I used to regularly publish Vim W32 binaries for new patchlevels of Vim, I used them on W98 at first, then on XP, and it is true that I had some problems with Unicode (in both gvim and Console Vim) as long as I used the Borland compiler, which apparently lacked some multibyte entry points; but then I switched to the make_cyg.mak makefile and the Cygwin cross-compiler (which is actually a MinGW compiler), and after that I never had any more systematic problems, even though I always compiled both a vim.exe and a gvim.exe together, and used them both. Then Steve Hall continued that tradition of dual vim/gvim compiles after taking back the torch fallen from my hands when, at some point in Vim 6.4 and 7.0aa history, my laptop's battery went belly-up and I had to send the box from Brussels to somewhere near Venlo for a few weeks. AFAIK, those vim.exe (console) builds weren't systematically more buggy than the corresponding gvim.exe (GUI+OLE) builds compiled from the same sources. What I do agree with is the recommendation not to edit the makefiles. The variables which could be set by editing the makefiles can also be set on the make command-line or in the environment, and personally I prefer that, because not modifying the makefiles means that any makefile patches will apply cleanly. The only source file which I sometimes edit (and that reluctantly, only because I haven't found a better way) is src/feature.h, in order to select non-standard +/- features, in my case -tag_old_static and (on Linux) +xterm_save, which seem rather harmless choices to me. Oh, I also use one "nonstandard" patch, namely Bill McCarthy's additional float functions, but I'm confident that if ever that patch creates something more than a "line offset" error in the standard ones, Bill (or someone) will publish a new version of it. Best regards, Tony. -- ASHes to ASHes, DOS to DOS. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
