XCode 3.1 and Ruby Error

Posted by Jake Good
on Aug 11, 08

Technical post for Google Searches and my own personal record

If you fire up XCode, start a new Cocoa project, and hit build... and get an error that looks like this:

error: can't exec '/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings' (No such file or directory)

Then either the installer failed (less likely) or you have an alternate Ruby in your path and you have removed your original /usr/bin/ruby that came with OS X.

So what you need to do is symlink your new Ruby to that same location...

ln -s /opt/local/bin/ruby /usr/bin/ruby

Now your XCode project should build!

Comments

Leave a response

  1. Andy Gaskell – Aug 11 08 @ 10:49AM
    Why would one remove the version of Ruby that comes with OS X or use an alternate version?
  2. Jake Good – Aug 11 08 @ 01:09PM
    When you start to do "real" ruby development on OS X, you start getting into using a package manager for other software libraries and binaries. Such as Fink and MacPorts... Then when you actually install packages that require ruby, the latest ruby (or matched version) will be linked against.... keeping your version in sync.

    And aside from that, you may need a version of ruby that is different than what the OS vendor dictates. And in that case, you'll run into the same problem.

    It does, unfortunately, render some of the built in features useless if the Frameworks don't match up or work together perfectly...
Comment