tag:blogger.com,1999:blog-4238494280010469357.post1200340791050524852..comments2008-04-23T08:59:27.588+12:00OneSadCookiehttp://www.blogger.com/profile/04354982399760362605noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4238494280010469357.post-61949724261859418972008-04-23T08:59:00.000+12:002008-04-23T08:59:00.000+12:00If you're building against the 10.4u SDK, you can't use Ruby.framework because it didn't exist; you'll need to use the unix-style includes and library.<BR/><BR/>If you're building against the 10.5 SDK, the fix provided in the post seems to do the trick.<BR/><BR/>If you're building on 10.5 without an SDK, the framework works fine.OneSadCookiehttp://www.blogger.com/profile/04354982399760362605noreply@blogger.comtag:blogger.com,1999:blog-4238494280010469357.post-19267373445804220512008-03-28T03:50:00.000+13:002008-03-28T03:50:00.000+13:00Kind of a stretch, but have you had any luck building against Ruby.framework? I can't seem to get my app to see its headers without pointing it to the absolute path, which kind of kills the point of using a framework.sjmlhttp://www.blogger.com/profile/08051686514474987791noreply@blogger.com