ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

How To Develop OS X Apps with MacRuby and Xcode 4.x

Updated on September 23, 2012

Apple did a wonderful thing recently; it does a lot of wonderful things but this is really great: Apple officially threw its support to Ruby with its own version of the language: MacRuby. The framework is included in the new release of XCode 4, which is available once you upgrade to OS X Lion. This is the second attempt by Apple to create its own version of the language that would run on their Objective-C runtime having first attempted to bridge (interface) the two languages. They had named that version: RubyCocoa. That version was slow and had many design flaws.

This new version is fast and interfaces directly with the Objective-C engine. It takes full advantage of the Objective-C API and garbage collector. The down side, it is doesn’t run on IOS devices.Yet. The other down side is that Apple is introducing the language as a private framework. This means that you have to include the framework in your package, which greatly increase the size of the package when you deploy your app locally; your computer or network, or through the Apple App Store.

Unlike, Objective-C, there are a couple of tweaks that must be performed to get the MacRuby App running.

1- Remove the I386 from the Valid Architectures
2- Add a Build Target to the Deployment Scheme

To help you get going I will walk you through the process; I will create a new app: Rubies.

Create a new Ruby app

Launch XCode 4 (you can upgrade your environment once you upgrade to Lion OS X). Select to create a new XCode Project. Next select the OS X node and select Applications to view the list of templates for Applications, select MacRuby Application framework and click the “Next” button.

In the next screen, provide a Name for the app and select the Category (this is for the App Store). Also enter a Company identifier, again for the App Store. This is similar to a Package in Java or a Namespace in the Microsoft .Net framework. The App name and Company are combined to create the Bundle Identifier.

In the next screen, you can add your project to a local Git repository, or deselect that option and click the “Create” button to create the project.

Add an app icon

Once the basic app is created, you can add an App icon. Right-click on the App Icon placeholder and choose “Select File”.

Change the Valid Architecture

To make your Ruby app compile and run successfully, you to remove the I386 architecture from the Valid Architectures. Select the your App name from the Project node and select “Build Settings”.

Double click on the Valid Architecture value (top level to modify both the Debug and Release architectures). Select “I386” and click the remove button ( a Minus symbol) on the bottom left of the dialog box. Click “Done” to save your change and close the dialog box. The Valid Architectures should only indicate the x86_64 architecture since OS X only supports 64 bit processing.

Add a deployment Plan

The next configuration that needs to be done is to add a Deployment Plan to the project. Select the project scheme by clicking on the Scheme selector button on the toolbar (next to the run & stop buttons). Select “Edit Scheme”. Next select the “Build” node in the scheme configuration panel and click the “+” symbol. Once the next dialog box opens, select the Deployment scheme if its not in your configuration or select your project scheme if it is not in your project. Both are required.

Under the “Run” node in the Scheme editor, make sure that your main executable is selected for all Schemes. In the following example, there are two schemes, rubies and Deployment. You need to select the executable in the Executable field in both Schemes. Select each scheme from the Scheme selector and select the executable in the Executable field.

Click the “Ok” button to close the dialog

Click the Run button to test your app before moving on to the next step.

Package your App

The last bit of work is to package your app for deployment to your system (Application) or the App Store (Package). You need a Developer ID from Apple to actually submit to their Store.

Select the Archiving menu option icon. Next select your project and click on Share. In the next screen select “Application” and save your app wherever you want on your system. Finally, navigate to the location with Finder and double click on your app to launch it.


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)