On 24/11/09 01:43, pansz wrote: > > bill lam 写道: >> $sudo apt-get build-dep vim # for console mode vim only >> $sudo apt-get build-dep vim-gnome # for gnome gvim as well > > That makes no difference in ubuntu. > > i.e. "sudo apt-get build-dep vim" is enough for make a gvim. (a gtk version) > > The only difference between gtk version and gnome version is the session > support. to enable gnome session support you should edit the Makefile or > give command-line option to .configure, no additional dependencies required. > > Compiling vim on Ubuntu is a very easy task and it definitely do not > require an expert. Following my instructions do (much simpler): > > The first time to compile. > 1. sudo apt-get build-dep vim > 2. cd > 3. svn co https://vim.svn.sourceforge.net/svnroot/vim/vim7 > 4. cd vim7/src > 5. vi Makefile > 6. make > 7. sudo make install > > If you're using ubuntu, everything should work after that. > if you want to edit any options, do that in precedure 5. > > if you want to upgrade your vim7 later: > > 1. cd ~/vim7 > 2. svn update > 3. make > 4. sudo make install > > then you have upgraded your vim to the newest version. > > Those instructions just complicate things, my instructions make every > average user capable to compile vim.
Again, not every Linux user has a distro which manages its packages by merans of apt-get. Also, I intentionally _don't_ give command-line parameters to configure, nor do I hand-edit the Makefile: it seems easier to me (and less error-prone, especially when _keeping_ Vim up-to-date by recompiling it) to have make itself invoke configure, with parameters set in the environment so that if make decides to run configure a second time (it happens if there have been changes in configure.in etc.), you'll get the same configure options. Avoiding handmade changes to the Makefile also ensures that _patches_ to the Makefile will apply cleanly. Best regards, Tony. -- The difference between this school and a cactus plant is that the cactus has the pricks on the outside. -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
