MacVim-Yosemite-Python should link with system ruby too

[CarterLi]

I tried MacVim-Yosemite-Python.tar.gz. It didn't work because:

% mvim
dyld: Library not loaded: /usr/local/lib/libruby.2.1.0.dylib
  Referenced from: /Applications/MacVim.app/Contents/MacOS/Vim
  Reason: image not found
[1]    2069 trace trap (core dumped)  mvim

Why do a version which targets system python requires homebrew ruby?

I tried MacVim-Homebrew-Python-2.7.8.tar.gz with homebrew python installed. It didn't work too for the same reason.

OS: OSX 10.10.2

[CarterLi]

I did try brew install ruby, but ruby-2.2.0 was installed instead of ruby-2.1.0. Thus didn't help.
MacVim-Basic.tar.gz works though

[genoma]

Yes you are right, the correct behaviour should be linking the default Ruby Yosemite version when i build MacVim with Yosemite Python.

I did try brew install ruby, but ruby-2.2.0 was installed instead of ruby-2.1.0. Thus didn't help.
MacVim-Basic.tar.gz works though

Thats because the latest build has been compiled when Ruby "brewed" version was 2.1.0 and i didn't noticed any problem because for the past few months i've used mainly Vim through terminal instead of MacVim.

The problem was a garbled Ruby installation on my Mac, i've fixed the problem in the latest release... hopefully.

I will try to fix both the issues today building an updated set of MacVim binaries.

[genoma]

The latest release should have the correct Ruby version linked in both binaries (Yosemite vanilla and Homebrew).

[CarterLi]

Tested and worked fine.
Thinks for this good project & quick fix

[CarterLi]

Just a suggestion:
Can we provide another version which copies those homebrew dylibs into MacVim.app to avoid the dependency hell?

[genoma]

This goes beyond my programming knowledge i fear and i'd like to keep this version as close as possible to the original MacVim (which should change project maintainer soon). That's because it will be a lot easier to merge the original MacVim into this one and vice versa.

This fork has been made for my obsession to keep updated MacVim as i keep my Vim build with the multiple weekly patches developed by Bram and the Vim community, i've only replicated the way Björn has used Git to merge Vim development with MacVim resolving a couple of merge conflict.

Lastly, i've been awfully busy for the past few months and the build error was completely my fault (a wrongly linked Python version with Homebrew and i didn't pay attention to what version was linked). I've changed the way i build the releases and it should be easier to spot an error in linked libraries.

Anyway thanks for spotting this error and feel free to report any other build issue in future.

[CarterLi]

This goes beyond my programming knowledge i fear and i'd like to keep this version as close as possible to the original MacVim

Oh yes. Then another suggestion: Is it ok to link dylibs with /usr/local/lib/libruby.dylib instead of version specified /usr/local/lib/libruby.2.1.0.dylib? I assume that it should be ABI-compatible between small bugfix-only releases...

the original MacVim (which should change project maintainer soon)

Glad to see it! There are many awesome PRs opening. I expect they get merged soon.