Fair enough, I did not realize that you'd already deployed an app based on MacRuby and had already received bug reports (which suggests that the number of 32 bit users is clearly non-zero, at least!). Have you filed a ticket in trac with a reduction (e.g. the minimum code necessary to demonstrate the problem) yet? That will allow us to track and prioritize the work for possible inclusion in 0.9 (or later, depending on how things go).
Thanks, - Jordan On Jan 31, 2011, at 2:41 AM, Richard Sepulveda wrote: > 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" <j...@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-7977a32bd...@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] > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
