Skip to content
This repository

Build fails after updating Xcode to 4.3.3 #107

Watson1978 opened this Issue June 12, 2012 · 27 comments

After updating Xcode to 4.3.3,
build fails at main.m which say "'MacRuby/MacRuby.h' file not found".

Mark Rada

You need to add /Library/Frameworks to the framework search path.

Mark Rada

I should elaborate more. I believe this is related to sandboxing, we shouldn't be using /Library/Frameworks/ anymore. I would have to go over the documentation to find out the new recommended behaviour though...

Geoffrey Roguelon


When i try to connect objects UI with methods and outlets, nothing happen, even if press CTRL.

This problem can it be the cause?



After installing/updating Xcode, you should reinstall MacRuby.

Geoffrey Roguelon

Ok, I've reinstalled MacRuby 0.12 but I get MacRuby.h not found. Where do I add /Library/Frameworks/ in framework search path ?


Geoffrey Roguelon

Sorry, I've found in Build settings of project settings...


I thought a way as not affect for project which have been already created , or new project:

ln -s /Library/Frameworks/MacRuby.framework /Applications/

I don't know this way is correct....

Michael Simms

I've added/Library/Frameworks and still getting MacRuby.h not found

Semyon Perepelitsa

Thanks, worked for me. @simmsmoapp, did you click on the checkbox? Here is a screenshot for reference.

search path

Michael Simms

Yes that worked, thanks

Julio Terra

that worked for me as well. Thanks for the screenshot.


thanks ,that work well


I have thought about this issue many times, I think good that framework search paths is added into Xcode4 template to solve this issue.
If we will found the better stuff, this issue would be improved with it.

Adrian Petrescu apetresc referenced this issue from a commit in MacGo/MacGo August 12, 2012
Adding /Library/Frameworks to search path.
Apparently required in XCode 4.4 due to bug MacRuby/MacRuby#107.
Luke Hamilton

@semaperepelitsa Thanks for the screenshot, that worked a treat! :)

Dru Nelson

+1 - yep that worked on Xcode 4.5.1 and MacRuby 0.12 for an older project

Hiram Castelo

The issue is still happening on XCode 4.5.1 and MacRuby 0.12. The search path is not automatically in the project created from template.

James Ratcliffe

I have this issue with Xcode 4.5.2 (and MacRuby 0.12).

Mark Rada ferrous26 closed this November 12, 2012
Mark Rada

This is a fixed issue in master. You can install a nightly build to get the fixes.

Mark Rada

I should have also mentioned that existing projects will need to add MacRuby.framework to the framework search path manually. Good instructions on how to do this are given above.


If I update with the recursive option as described above, I get an error
Argument list too long: recursive header expansion failed at /Library/Frameworks/MacRuby.framework/Versions/0.13/usr/share/ri/1.9.2/system/WEBrick/HTTPAuth/Authenticator.

I have installed the latest nightly build - How do I fix this?

Penn Su

Installing the latest nightly build today, still doesn't add /Library/Frameworks to its search path on new macruby application

Keith Smiley

Seems like this could be fixed in the project template

Mark Rickert

Just adding a screenshot for people on Xcode 4.6.2 since the other screenshot is a bit outdated.

screen shot 2013-05-06 at 10 56 42 am

Dewayne VanHoozer

Please explain it to an old man .... and talk slowly. I have installed MacRuby 0.12 via RVM. I have Xcode 4.6.2 installed. There are no MacRuby templates showing in xcode. Where is the install templates script that fixes this?

Dru Nelson
drudru commented June 11, 2013

@MadBomber - RVM doesn't install MacRuby system wide. Xcode is system wide.

  1. Shut down Xcode. It cannot be running while you install.
  2. Install MacRuby without using RVM.


BTW, I like RVM too, I use it for all my non-macruby projects. This just isn't a good fit for the Xcode issue.

Dewayne VanHoozer

I smell bacon! Thank you.

Nikita Dudnik

I had this problem with XCode 4.6.3.
Adding "/Library/Frameworks" to Frameworks Search Paths fixed it though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.