I'm now on master in order to get the BridgeSupport fix, but my archived applications are erroring now due to a LOAD_PATH issue. Basically, the embedded framework is in: Elephant.app/Contents/Frameworks/MacRuby.framework/Versions/Current But the LOAD_PATH for the app is now: Elephant.app/Contents/Frameworks/MacRuby.framework/Versions/0.11 It manifests as not being able to require any files in the stdlib. Tonight I'll be able to submit a reproduction of the issue (have to run out now) but in the meantime, any ideas as to what the cause might be? Thanks, -- Nathaniel Talbott <:((><
On Sun, Apr 17, 2011 at 12:07 PM, Nathaniel Talbott <nathaniel@talbott.ws> wrote:
Tonight I'll be able to submit a reproduction of the issue (have to run out now) but in the meantime, any ideas as to what the cause might be?
After doing a bit of poking around and failing to find the root of the problem, I decided to just fix up $LOAD_PATH by adding the following at the top of rb_main.rb: $LOAD_PATH.collect!{|d| d.sub(%r((MacRuby.framework/Versions/)[^/]+), '\\1Current')} I'd still love to see a permanent fix; here are an app and project that reproduce the problem: http://dl.dropbox.com/u/438257/LoadPathTest.zip With a MacRuby build of master installed, I created the by simply creating a new MacRuby app in Xcode, fixing it to so it will produce an Archive, and then adding a `require "fileutils"` to the top of AppDelegate.rb. Archiving the project and then running the resulting application will print this to the Console: 4/17/11 5:11:35 PM [0x0-0xcf6cf6].com.terralien.LoadPathTest[6324] /Users/ntalbott/Desktop/LoadPathTest.app/Contents/Resources/rb_main.rb:18:in `block': no such file to load -- fileutils (LoadError) Let me know if you need any more info, -- Nathaniel Talbott <:((><
On Apr 17, 2011, at 2:18 PM, Nathaniel Talbott wrote:
On Sun, Apr 17, 2011 at 12:07 PM, Nathaniel Talbott <nathaniel@talbott.ws> wrote:
Tonight I'll be able to submit a reproduction of the issue (have to run out now) but in the meantime, any ideas as to what the cause might be?
After doing a bit of poking around and failing to find the root of the problem, I decided to just fix up $LOAD_PATH by adding the following at the top of rb_main.rb:
[…] Thanks for finding this also! It looks like the recent change to macruby_deploy in order to conform to new AppStore submissions broke the load path relocation. I corrected the problem in https://github.com/MacRuby/MacRuby/commit/f024e510389140e090aa3404ed18744fc6... MacRuby core has a very intensive test suite, but sadly we don't have any test for macruby_deploy yet. Maybe we should consider writing some at some point to avoid this kind of regressions. Laurent
On Sun, Apr 17, 2011 at 9:56 PM, Laurent Sansonetti <lsansonetti@apple.com> wrote:
Thanks for finding this also! It looks like the recent change to macruby_deploy in order to conform to new AppStore submissions broke the load path relocation.
Perfect - the fix works great. Thanks! -- Nathaniel Talbott <:((><
participants (2)
-
Laurent Sansonetti
-
Nathaniel Talbott