Building gvim 7.4 on CentOS 6.4

I am trying to build gvim7.4 from a source on a box working with CentOS 6.4. I followed the instructions mentioned here to create a virtual local area network. The executable "vim" is just fine, but "gvim" is nowhere to be seen. I tried everything I could find on google but it doesn't seem to help.

Should gvim be built in any other way (other than the usual configure / make way)? Or is there some kind of obscure trick for creating an executable for gvim?

My OS: CentOS 6.4. Has all the necessary X / devel materials. Used command:

./configure --prefix=/usr --with-compiledby="megazoe" \ --with-features=huge --enable-rubyinterp \ --enable-pythoninterp --enable-python3interp \ --enable-gui=gnome2 --enable-luainterp \ --enable-perlinterp --enable-cscope 

Configure stdout has things related to X:

 checking if X11 header files can be found... yes checking for _XdmcpAuthDoIt in -lXdmcp... no checking for IceOpenConnection in -lICE... yes checking for XpmCreatePixmapFromData in -lXpm... yes checking if X11 header files implicitly declare return values... no checking size of wchar_t is 2 bytes... no checking --enable-gui argument... GNOME 2.x GUI support checking --disable-gtktest argument... gtk test enabled checking for pkg-config... /usr/bin/pkg-config checking for GTK - version >= 2.2.0... yes; found version 2.18.9 checking for libgnomeui-2.0... yes checking for FreeBSD... no checking X11/SM/SMlib.h usability... yes checking X11/SM/SMlib.h presence... yes checking for X11/SM/SMlib.h... yes checking X11/xpm.h usability... yes checking X11/xpm.h presence... yes checking for X11/xpm.h... yes checking X11/Sunkeysym.h usability... yes checking X11/Sunkeysym.h presence... yes checking for X11/Sunkeysym.h... yes checking for XIMText in X11/Xlib.h... yes X GUI selected; xim has been enabled checking for CYGWIN environment... no 

Make does not cause any error, "vim" is created just fine. Only, there is nowhere to be seen! I can use the -g switch with vim for the GUI instance [vim -g], but this is not gvim, using the GNOME line and works, which is what I want. Shouldn't I create "gvim" because --enable-gui = gnome2 is used? Or is it a completely different beast?

Any suggestions on how to get around this problem?

Thanks!

+6
source share
1 answer

The trick seems to set the correct vimruntime directory when calling make and has below

 --enable-gui=gnome2 --with-x=yes 

in the list of switches for the script configuration.

Here is my test build script, which seems to give the desired result.

 mkdir /tmp/vimbuild; cd /tmp/vimbuild wget -c ftp://ftp.vim.org/pub/vim/unix/vim-7.4.tar.bz2 tar -xjvf vim-7.4.tar.bz2 cd vim74 \rm -rf src/auto/config.cache make clean ./configure --prefix=/usr --with-compiledby="megazoe" \ --with-features=huge --enable-rubyinterp \ --enable-pythoninterp --enable-python3interp \ --disable-tclinterp --with-x=yes \ --enable-xim --enable-multibyte \ --enable-gui=gnome2 \ --enable-luainterp --enable-perlinterp \ --enable-cscope \ --enable-netbeans 2>&1 make -j20 VIMRUNTIMEDIR=/tmp/vimbuild/vim74/runtime/ if [ -f src/vim ] then \cp -f src/vim src/gvim strip src/gvim ./src/gvim & fi 

The presence of the final executable file named "gvim" is important, otherwise it must be called as vim -g to work in graphical mode.

+7
source

Source: https://habr.com/ru/post/952658/


All Articles