Skip to content

Instantly share code, notes, and snippets.

@samkrishna
Last active December 16, 2015 20:49
Show Gist options
  • Save samkrishna/5495565 to your computer and use it in GitHub Desktop.
Save samkrishna/5495565 to your computer and use it in GitHub Desktop.
RestKit re-virginity

I got to work on RestKit 0.20.0 a little bit with @BlakeWatters back in the winter.

I'm cranking it up again for another set of projects and I noticed that trying to build the default gem set caused a crash.

Here's my environment:

  • OS X: 10.8.3
  • Xcode: 4.6.2
  • Xcode CLI Tools: 4.6.2
  • Homebrew-installed ruby 2.0.0-p0

It seems as if ruby 2.0.0-p0 was the culprit. It looks like CocoaPods and the debugger gem would be happy at 1.9.3-p392. However, as of right now, it doesn't seem as if Homebrew has an easy way to roll back to an earlier version (short of uninstalling and installing a specific target). Yuck.

rbenv to the rescue!

Uninstalling Homebrew's ruby and then setting up the environment to default to rbenv instead enabled the RestKit-dependent gems to build clean. Now rbenv manages the ruby environments and Homebrew manages everything else.

At some point in this process, I needed to install Bundler to get the Gemfile to actually execute.

After that, I needed to install rake 10.0.3 (b/c the latest rev. at 10.0.4 caused it to fail). And then I tried it again:

$ bundle install

And all the gems installed great. However, when I tried to run

$ rake server

Everything still failed. Finally, I followed the warning message and ran:

$ bundle exec rake server

And the test server finally started.

And then I was able to run the unit tests just fine (well, apart from their own crashes, but you get the picture).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment