Closed digitalresistor closed 10 years ago
adamv
commented
11 years ago So, I'm not sure what's going on here, but we should add an explicit --name=value option to vim and macvim for explicitly selecting a Ruby to compile against, rather than relying on whatever is first in the path.
dymv
commented
10 years ago I have problems with Command-T plugin(crash with SIGSEGV).
vim's version contains:
Compilation: /usr/bin/clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -Os -w -pipe -march=native -mmacosx-version-min=10.8 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: /usr/bin/clang -L. -L/usr/local/opt/libyaml/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libksba/lib -L/usr/local/opt/openssl/lib -L/usr/local/lib -Wl,-headerpad_max_install_names -o vim -lm -lncurses -liconv -framework Cocoa -framework Python -lruby.1.9.1 -lobjc -L/Users/dymv/.rvm/rubies/ruby-1.9.3-p484/libmacvim's version contains:
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -I/System/Library/Frameworks/Tcl.framework/Headers -D_REENTRANT=1 -D_THREAD_SAFE=1 -D_DARWIN_C_SOURCE=1
Linking: clang -L. -L. -L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/System/Library/Frameworks -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon -lncurses -liconv -framework Cocoa -fstack-protector -L/usr/local/lib -L/System/Library/Perl/5.12/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -framework Python -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework RubyWhat params should I specify along with brew install to use ruby 1.9.3 in mvim as well as in vim?
dymv
commented
10 years ago brew install vim takes into account ruby's version I choose via rvm, but brew install macvim does not.
mistydemeo
commented
10 years ago Macvim is a separate issue. I believe it only supports framework Ruby builds, which in effect means only rubies that come with OS X.
dymv
commented
10 years ago @mistydemeo So, to use plugins in both MacVim and vim I should compile both of them with ruby 1.8 linked?
adamv
commented
10 years ago @dymv The Command-T plugin is picky about which version of Ruby it gets compiled with. We're definitely willing to review pull requests to fix or improve how we compile Vim, but we don't really provide troubleshooting support for Vim + Command-T, soryr.
adamv
commented
10 years ago Also, we don't provide troubleshooting support for vim plugins in general, so I'm not sure what the implications are of trying to share them between Vim and MacVim.
According to the brew file for vim:
So I set the ruby 1.8 first in my path, since it seems like MacVim is automatically compiled against it.
I want my plugins to work across both vim and macvim, so I wanted to compile against ruby1.8, so I followed the directions and set it first in my path, however this fails to compile. I am not sure what the issue is, or if there is some other flag or setting I am missing. Help would be appreciated :-).