That makes perfectly good sense but i unfortunately started selling a MacRuby app on the App Store
for i386 and 64 bit machines. And a few people are experiencing this issue. I was just hoping
for a quick workaround to make them happy. And I would discontinue selling the 32 bit version
on the next release.
But i can't see anything obvious other than rewriting all of my NSDate based code in Objective-C or
waiting for a fix. i include the MacRuby framework in my Pkg so that is possible.
Richard
Message: 2
Date: Sun, 30 Jan 2011 22:08:38 -0800
From: "Jordan K. Hubbard" <jkh@apple.com>
To: "MacRuby development discussions."
<macruby-devel@lists.macosforge.org>
Subject: Re: [MacRuby-devel] Strange NSDate behavior building 32 bit v
64 bit
Message-ID: <D31EF44C-06F8-45B1-83B4-7977A32BD53F@apple.com>
Content-Type: text/plain; charset="us-ascii"
I suppose this begs the question: Does anyone really *require* 32 bit support for MacRuby at this point? SnowLeopard is already the minimum supported config, and the only Intel 32 bit-only platforms (very early MacBook and Mac Mini configurations) are several years old now. I don't want to sound like an unfeeling ogre to anyone who actually has such a configuration, mind you, but how big of an installed base does this really represent?
- Jordan
On Jan 30, 2011, at 8:49 PM, Vincent Isambart wrote:
1. Modified the Valid Archetectures to "i386 x86_64"
There's a simple way to run macruby (or any other program) on the
command line in 32 bits: just add "arch -i386" before the name of the
program to execute:
$ macruby -v
MacRuby 0.9 (ruby 1.9.2) [universal-darwin10.0, x86_64]
$ arch -i386 macruby -v
MacRuby 0.9 (ruby 1.9.2) [universal-darwin10.0, i386]