Using Rubymine on OXS Mavericks

TL;DR: I had to move XCode to the trash and reinstall it via the app store, but even then I had to install gems via the command line with the -Wunused-command-line-argument-hard-error-in-future  flag, instead of inside RubyMine.

This weekend I learned Ruby, and I really enjoyed it. I did have a few teething problems with my environment, though.

I usually prefer not to get tied into any particular IDE so develop using advanced text editors like Sublime Text, but because I had to learn Ruby quickly I went for something that would let me hit the road running. I chose RubyMine purely based on its popularity and support for Cucumber.

I started seeing problems as soon as I started trying to install gems via RubyMine. I was getting build failures, like the following:

The last line seemed strange – I’d been using command line developer tools for ages. That aside, I tried reinstalling again anyway:

That seemed to work – I did get a dialog asking me if I wanted to install command line developer tools and proceeded to do so. I was still getting the error when trying to install gems in Rubymine, though, so I though I’d try via the command line, but I got the same error.

I’m using XCode 5.1 right now, but it occurred to me that I had been, at some stage using beta versions of XCode, and some things had been moved around inside the XCode.App in some of those versions. I moved XCode to the trash, and reinstalled it via the app store. 20 minutes later I had a different message in RubyMine:

The hint this gave me was in the “this will be a hard error in future”. So, what if I already had this “future” version of make? It would seem strange that the message would appear at all if the restriction had already been imposed, but I thought I’d check it out. Let’s try to install the gem on that command line with the -Wunused-command-line-argument-hard-error-in-future  argument:

Success!

Note: I also found out during this exercise that recent versions of XCode include the command line tools, so there’s no need to install them separately.

Leave a Reply

Your email address will not be published. Required fields are marked *

*