"Reply-To" is overridden by Google Groups so I'm adding vim-dev as "To:". 
Please send followup email there.

Geshtar Kerensky wrote:
> I hope this is best list to post this to, this seemed slightly more 
> appropriate
> than vim-development since I am not really trying to develop vim, just build 
> it.
> 
> I have been trying to compile vim with gtk2 but have been having issues that
> googling has not been able to solve.  I think it is probably a very
> simple problem,
> but I have been spoiled by package management systems and am therefore not
> very fluent at building large programs by hand (e.g. - using configure).
> 
> Despite having compiled gtk 2.8.20, configure keeps saying it cannot find it.

Configure is a script, different for each package. Vim configure never 
compiles the GTK packages; if configure compiled them, it must have been a 
different configure, from some other source and in some different directory.

> 
> I have tried all sorts of configure options, but to no avail.
> 
> Here are some examples:
> 
> ./configure --prefix=/nfs/fc/home/cbwallac/bin/vim71 --enable-gui=gtk2
> --enable-cscope
> --with-gtk-prefix=/nfs/fc/home/cbwallac/bin/gtk-2.8.20/

from the errors in the config log below, it looks like you have a spurious 
slash at the end here

> 
> OUTPUT:
> 
> checking --enable-gui argument... GTK+ 2.x GUI support
> checking --with-gtk-prefix argument... /nfs/fc/home/cbwallac/bin/gtk-2.8.20/
> checking --with-gtk-exec-prefix argument... no
> checking --disable-gtktest argument... gtk test enabled
> Using GTK configuration program
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config
> checking for pkg-config... (cached) /nfs/fc/home/cbwallac/bin/pkg-config
> checking for GTK - version >= 2.2.0... auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> no
> checking for GTK - version >= 1.1.16... auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> auto/configure: line 1:
> /nfs/fc/home/cbwallac/bin/gtk-2.8.20//bin/gtk-config: No such file or
> directory
> 
> 
> Why is configure trying to use gtk-config when looking for gtk version
>> = 2.2.0?  To the
> best of my understanding, gtk2 does not have gtk-config and uses
> pkg-config instead.

IIUC, pkg-config is proprietary Debian (also used on Ubuntu). Configure should 
be looking for "something" which is supposed to exist in every GTK2 
development environment.

> 
> I have also tried adding the pkg-config location for my gtk libraries
> to the environment
> variable (this has helped me on numerous other compilations, but not
> here apparently)
> 
> ./configure --prefix=/nfs/fc/home/cbwallac/bin/vim71 --enable-gui=gtk2
> --enable-cscope
> PKG_CONFIG_PATH=/nfs/fc/home/cbwallac/bin/gtk-2.8.20/lib/pkgconfig
> 
> OUTPUT:
> checking --enable-gui argument... GTK+ 2.x GUI support
> checking --with-gtk-prefix argument... no
> checking --with-gtk-exec-prefix argument... no
> checking --disable-gtktest argument... gtk test enabled
> checking for gtk-config... (cached) /opt/gnome/bin/gtk-config
> checking for pkg-config... (cached) /nfs/fc/home/cbwallac/bin/pkg-config
> checking for GTK - version >= 2.2.0... no
> checking for GTK - version >= 1.1.16... yes; found version 1.2.10
> 
> 
> Any ideas on how to make configure find gtk2 would be greatly appreciated.
> 
> Thanks.

Try removing the slash after 2.8.20, and make sure that the package gtk2-dev 
(or gtk2-devel or whatever your distro calls it) is installed. Or if your GTK2 
packages are located "at a standard location" on your filesystem, you could 
omit the --with-gtk-prefix argument altogether.

I use the following settings, which I set as environment variables, by 
sourcing -- not running -- the following script before running make, and I 
have no problems compiling gvim with GTK2/Gnome2 GUI on openSUSE 10.3 (or, 
until last week, openSUSE 10.2). (Note: make config, make reconfig and, if no 
config cache exists, plain make with no target, all invoke configure in the 
course of their operations.)

#!/bin/bash
export CONF_OPT_GUI='--enable-gnome-check'
export CONF_OPT_PERL='--enable-perlinterp'
export CONF_OPT_PYTHON='--enable-pythoninterp'
export CONF_OPT_TCL='--enable-tclinterp --with-tcl=tclsh8.4'
export CONF_OPT_RUBY='--enable-rubyinterp'
export CONF_OPT_MZSCHEME='--disable-mzschemeinterp'
# export CONF_OPT_PLTHOME='--with-plthome=/usr/local/plt'
export CONF_OPT_CSCOPE='--enable-cscope'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
export CONF_OPT_FEAT='--with-features=huge'
export CONF_OPT_COMPBY='"[EMAIL PROTECTED]"'
# export CONF_ARGS='--with-modified-by=""'

# need to patch feature.h
# to disable +tag_old_static: comment out:
# # define FEAT_TAG_OLDSTATIC
# at line 360 (or about)
# to enable +xterm_save: uncomment:
# /* #define FEAT_XTERM_SAVE */
# at line 831 (or about)



Best regards,
Tony.
-- 
CLONE OF MY OWN (to Home on the Range)

Oh, give me a clone
Of my own flesh and bone
        With the Y chromosome changed to X.
And when she is grown,
My very own clone,
        We'll be of the opposite sex.

Chorus:
        Clone, clone of my own,
        With the Y chromosome changed to X.
        And when we're alone,
        Since her mind is my own,
        She'll be thinking of nothing but sex.
                -- Randall Garrett

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui