[slim-vim] Compiling with GUI?

Brad Beveridge brad.beveridge at gmail.com
Tue Jul 18 20:30:33 CDT 2006


On 18/07/06, Richard Newman <rnewman at tellme.com> wrote:
> Hi all,
>
>    Compiling Larry's vim70 repo on OS X/Intel, configure doesn't seem
> to want to enable the Carbon GUI. configure without GUI arguments
> picks X as the default GUI; using
>
> ./configure --without-x --disable-gpm --prefix=/usr/local/ --enable-
> gui=carbon  --enable-eclinterp --enable-perlinterp --enable-cscope --
> enable-rubyinterp --enable-tclinterp
>
>    gives
>
> checking for IceConnectionNumber in -lICE... (cached) yes
> checking if X11 header files can be found... yes
> checking for _XdmcpAuthDoIt in -lXdmcp... (cached) no
> checking for IceOpenConnection in -lICE... (cached) yes
> checking for XpmCreatePixmapFromData in -lXpm... (cached) yes
> checking if X11 header files implicitly declare return values... no
> checking --enable-gui argument... Sorry, carbon GUI is not supported
>
>    and builds a perfectly-functional terminal-only Vim.
>
>    Googling doesn't seem to yield an answer; on a Mac the Vim source
> is *supposed* to build Vim.app by default, so I'm a little confused.
>
>    Any thoughts?
>
>    Thanks,
> -R
Hi Richard, I run Intel OSX also.  I tried to build the carbon GUI
many moons ago, and never really got anywhere.  I currently just use
the console version of Vim (which I happen to prefer), my configure
line is
./configure --prefix=/opt/local --enable-eclinterp --disable-darwin

The other issue that you may run into is the async patch that Jim made
- I am not sure which frontends support async communication (which
Slim-vim needs), I know console and GTK work.  If you can live with
running a console based Vim, that is probably the path of least
resistance.

Cheers
Brad

-- 
Go and see "An Inconvenient Truth"
http://www.climatecrisis.net/


More information about the slim-vim mailing list