Oh, thanks a bunch for the answer. But I rather look for VIM with some GUI. I am looking for the best recipe to browse and learn Linux Kernel. Currently I am using VIM with cscope and trinity, which is _very_ efficient combination, but the lack of GUI is certainly a big downside. As for now, I think KDevelop is the best in all aspects except the memory... Still keep testing them.
Thanks, --- Kosta On Mon, Dec 26, 2011 at 7:47 AM, Tony Mechelynck <[email protected]> wrote: > On 25/12/11 17:39, Konstantin Zertsekel wrote: >> >> Hi all, >> >> Not sure if this list is correct, but I'll give it a try... >> >> I clones VIM QT by Rui Abreu Ferreira: >> $ git clone https://git.gitorious.org/vim-qt/vim-qt.git >> >> And just compiled it on Ubuntu 11.04 and got the below error: >> CC="gcc -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_QT -Iqt -I. >> -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore >> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui >> -I/usr/include/qt4 -I. -I. " srcdir=. sh ./osdef.sh >> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_QT -Iqt -I. >> -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore >> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui >> -I/usr/include/qt4 -I. -I. -O2 -fno-strength-reduce -Wall >> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/buffer.o >> buffer.c >> In file included from vim.h:1972:0, >> from buffer.c:28: >> globals.h:870:13: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or >> ‘__attribute__’ before ‘xic’ > > > globals:h > 853: #ifdef FEAT_XIM > 854: # ifdef FEAT_GUI_GTK > ... > 869: # else > 870: EXTERN XIC xic INIT(= NULL); > 871: # endif > ... > 876: #endif > > I don't know where XIC (type name) is defined. > > >> make[2]: *** [objects/buffer.o] Error 1 >> make[2]: Leaving directory `/home/kosta/my/dev/vim/vim-qt/src' >> make[1]: *** [myself] Error 2 >> make[1]: Leaving directory `/home/kosta/my/dev/vim/vim-qt/src' >> make: *** [first] Error 2 > > [...] > > I'm not sure the Qt port is still supported (last I heard, it wasn't), or by > whom. Try the following: > > 1. get Bram's official Vim source, see > http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial > > 2. (if not already done) install Gnome (including several -dev packages > needed to compile gvim; I'm not sure which apt-get command will get them all > for you but no doubt someone else will know) > > 3. check your configure options. I recommend configuring with > --enable-gnome-check, see > http://users.skynet.be/antoine.mechelynck/vim/compunix.htm > > 4. Compile (i.e. make) in your new Mercurial clone. Or if you have an > existing Mercurial clone of Vim and changed the configure options and/or the > set of available software packages since the last compile, run "make > reconfig" (and make sure that your configure options are set via environment > variables, see § 3 above). Configure will compile with GTK2 (if available) > in preference to any other GUI. > > > Best regards, > Tony. > -- > Violence is the last refuge of the incompetent. > -- Salvor Hardin -- 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
