On 26/12/11 11:46, Peter Odding wrote:
On 26-12-11 10:55, Tony Mechelynck wrote:
Well, why not use a GTK2/Gnome2 Vim GUI? I use that on openSUSE Linux,
and it compiles like a breeze. I'm sure the needed development packages
exist on your Ubuntu distro just like they exist on my openSUSE. I've
seen Ubuntu/Debian users post a oneline apt-get build-dep command meant
to install all packages needed to compile gvim with GTK2/Gnome2 on their
systems, only I haven't remembered it since SuSE uses a different
package management system (the YaST GUI/cursesUI or the zypper CLI).
Below is a summary of the commands I use to compile the latest gVim 7.3
from source on Ubuntu 10.04 should you be interested (the commands come
from a shell script ~/bin/build-vim which I run once every few weeks to
stay up to date):
sudo apt-get build-dep vim-gnome
sudo apt-get install autoconf
hg clone https://vim.googlecode.com/hg/ vim-sources
rather than clone from scratch every time, wouldn't it be enough to run
(except the first time of course)...
cd vim-sources
(continued)
hg pull -u
at this point in the script?
export CONF_OPT_FEAT='--with-features=huge'
export CONF_OPT_GUI='--enable-gnome-check'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
make -C src autoconf
make
sudo make install
- Peter
PS. I'm not sure you need the two lines referring to autoconf; feel free
to skip those and see if it works without :-). Also a heads up: The
build-dep line pulls in quite a lot of packages...
The Vim source comes with configure pre-built, you don't need to run
autoconf.
Building with a "dirty" objdir (not removing old objects) is faster: the
whole point of the make utility is that it recompiles only what has
changed. One caveat though: when configure changes, "make" will try to
rerun it, and give an error saying that configure values have changed:
remove src/auto/config.cache and rerun the make (which will again invoke
configure, but successfully). You should also "make reconfig" yourself
if the included libraries have changed significantly.
In contrast to the above, I run
hg incoming
frequently in the directory corresponding to your vim-sources, and then
I only pull and compile if there have been changes to what I use (no
need to recompile if there are no changes, or if the only changes are
for, let's say, Windows or EBCDIC).
Best regards,
Tony.
--
Under a government which imprisons any unjustly, the true place for a
just man is also in prison.
-- Henry David Thoreau
--
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
