Tony Mechelynck, 15.11.2008: > > On 15/11/08 17:50, Markus Heidelberg wrote: > > The master branch has already set --with-modified-by to "Vim extended", > > but there is also a #define MODIFIED_BY in feature.h. What is the > > difference between these two? Is this for configurations not using > > configure and should be set, too? > > --with-modified-by (in configure) sets a #define MODIFIED_BY in > src/auto/config.h. However, even though on Unix-like systems it is > recommended to use configure, it is possible to do it all by hand and > compile Vim without it. You would then uncomment the line in feature.h. > > Also, on Windows (when not generating Vim "for use only with Cygwin") > neither configure nor the top-level Makefile are used. Instead, there > are a number of makefiles in the src/ directory, one for each compiler > (including Make_cyg.mak when compiling for "native Windows" using Cygwin > gcc). These makefiles can set some options (such as featureset or which > interpreter interfaces to include) but you will probably have to set > MODIFIED_BY (if you want to use it) in feature.h in this case.
OK, thanks for the explanation. Then I'll use #ifndef MODIFIED_BY # define MODIFIED_BY Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
