Richard Hartmann, 07.12.2008: > Hi all, > > building vim_extended with the code checker patch fails: > > > % git checkout -b local/code_checking origin/vim > % git merge origin/code_checking > % ./configure --with-features=huge --enable-multibyte --enable-cscope \ > --enable-perlinterp --enable-pythoninterp --enable-rubyinterp \ > --prefix=/usr/local/vim_extended > % make
It doesn't fail for me with exactly this proceeding. > code_check.c:315: error: 'gui' undeclared (first use in this function) > code_check.c:364: error: 'gui' undeclared (first use in this function) FEAT_GUI is not defined, so gui.h is not included and gui_T gui is unknown. Some #ifdef FEAT_GUI are required. Doesn't configure find GTK or so? See vim.h line 100. Birgi, is the codecheck project still active? There are no new commits/patches on the Google Code project site since your announcement on the list. > Markus, please put the attached file into the git repo. In which branch, master? I already have plans to split the readme part on the gitweb interface into two: one for the most simple use of just the master branch as already done and another for creation of an own branch merging various feature branches as you did in the attached file. But I'd like to keep it short, forgoing all the things that aren't special for vim_extended like details in configuring Vim and setting up git. There is already enough documentation out there, a Vim novice won't use vim_extended anyway, a git novice though. Wednesday is my last working day, then I'll have more time even though I've so many plans. I wonder if it is better to activate the features by default. The Lua interface for example. I think it is, nobody wants to merge the lua branch for not using it, do you agree? I also think it would be better to patch src/auto/configure, then "make -C src autoconf" wouldn't be necessary anymore. This would also be the case, when the patch was integrated into mainline. Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
