Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't start GUI on Mac OS X 10.10 Yosemite #47

Closed
jarias opened this issue Oct 20, 2014 · 7 comments
Closed

Can't start GUI on Mac OS X 10.10 Yosemite #47

jarias opened this issue Oct 20, 2014 · 7 comments

Comments

@jarias
Copy link

jarias commented Oct 20, 2014

Firing up config GUI!
EXCEPTION! spawn ENOENT
Error: spawn ENOENT
    at errnoException (child_process.js:1001:11)
    at Process.ChildProcess._handle.onexit (child_process.js:792:34)
@tomas
Copy link
Contributor

tomas commented Oct 20, 2014

Looks like Yosemite updated the system Ruby location. What do you get with a which ruby on your system? Does /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby exist?

@jarias
Copy link
Author

jarias commented Oct 20, 2014

1.8 was updated since Mavericks you can use

/System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby which should always point to the system Ruby.

Also it might be good not to assume only one ruby is in the path (RVM, RBenv, etc)

@tomas
Copy link
Contributor

tomas commented Oct 20, 2014

Good to know. Unfortunately, we can't rely on RVM/Rbenv rubies as we need to require 'osx/cocoa' which is only available on the system one.

@jarias
Copy link
Author

jarias commented Oct 20, 2014

Even better, I was just wandering if you guys look it up from the PATH since rbenv and rvm both modify the PATH and can give you a different set of issues.

@tomas
Copy link
Contributor

tomas commented Oct 20, 2014

Actually, I use rbenv and after calling rbenv --init the path to the ruby binary gets replaced by a shim:

$ which ruby
/home/tomas/.rbenv/shims/ruby

That's why we need to use the full path to the system one. :)

@tomas
Copy link
Contributor

tomas commented Oct 21, 2014

Ok, so the problem is that both Ruby 1.8 and RubyCocoa were removed from OS X in Yosemite.

Last night I ported the GUI code from RubyCocoa to PyObjC and it seems to work fine. I'll be pusing a new release in a few days including this change as well as some other fixes.

@jarias
Copy link
Author

jarias commented Oct 21, 2014

Cool :)

@tomas tomas closed this as completed Oct 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants