[MacRuby-devel] macruby singleton_methods

2011-05-11 Thread anoiaque
Hi, Suppose: class User; def self.all;end end With Ruby 1.8, and 1.9.2 interpreters User.singleton_methods #=> [:all] With Macruby you get []. Normal ? Is it an issue to add ? Can we interpret 1.9.2 code with macruby and expect the same result ? Thanks. _

Re: [MacRuby-devel] macruby singleton_methods

2011-05-11 Thread Eloy Duran
Yes you can compare MacRuby against 1.9.2. I *think* the best would be to compare against 1.9 trunk, but Laurent might have to correct me on that. So yes, please file a ticket for this issue :) On Wed, May 11, 2011 at 1:24 PM, anoiaque wrote: > Hi, > > Suppose:  class User; def self.all;end end

Re: [MacRuby-devel] MacRuby Application .pkg install results in Unsupported Architecture

2011-05-11 Thread Daniel Westendorf
Thanks for taking the time to look into this Josh. I hadn't used the file command on my bundle contents. After doing this on a vanilla MacRuby app, I did not find any files that were not x86_64. Also, I've been installing the latest nightly builds of Macruby. I'm sure it is something silly that I'

[MacRuby-devel] Class MacRuby implemented in two locations

2011-05-11 Thread saugust
Hi Everyone,I am getting a strange error when I try to build a project. I made some minor changes to an application and now when I build the app I am getting this message:objc[5058]: Class MacRuby is implemented in both /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/libmacruby.

Re: [MacRuby-devel] macruby_deploy not embedding all of MacRuby

2011-05-11 Thread Kevin Colyar
I was able to fix this problem with the following script: #!/bin/sh APP="MyApp" SOURCE_BUILD_DIR="build/Release" TARGET_BUILD_DIR="build/Deploy" LOCAL="$SOURCE_BUILD_DIR/$APP.app/" REMOTE="$TARGET_BUILD_DIR/$APP.app/" rsync --progress $* -avzut $LOCAL $REMOTE --exclude .DS_Store --copy-links P

Re: [MacRuby-devel] Class MacRuby implemented in two locations

2011-05-11 Thread saugust
I figured out my issue. I had a buggy script running on a second thread which wasn't reporting the error. Is there a way to have a second thread throw an error back to Xcode when something goes wrong?   NSThread.detachNewThreadSelector('control_server:', toTarget: self, withObject: 'dummy')