On 2011-05-20, at 3:28 PM, Nat Brown wrote:
am i understanding the option being described here as manually forcing a pre-compile of .rb gems to .rbo cached to the gems directory (with caveats like no backtrace, ymmv)?
Almost. You lose backtraces right now, but that is a temporary tradeoff; eventually MacRuby will be able to give backtraces for pre-compiled code. Also, there is the auto_compile command in the plugin that automatically compiles gems as you install them.
anybody working on a generic (system-wide or per-user or configurable?) cache of arbitrary .rb -> .rbo similar to how rubyinline works, where llvm intermediaries being built are automatically cached and invalidated when the associated/underlying .rb changes?
i would be interested to help if somebody is already in-flight with that, or take a stab it if nobody is -- lmk pls.
That sounds interesting and potentially very useful, but not too difficult to do. Unfortunately I am already in the middle of too many different projects so I wouldn't be able to help much. :(
thx, n@
Good luck,
On Fri, May 20, 2011 at 12:07 PM, Mark Rada
<mrada@marketcircle.com> wrote:
Rspec 2.6 works on the macruby nightly builds.
Load times are partly due to rubygems being very slow on MacRuby and rspec being split into 4 gems (plus one other external gem).
The other problem is that you have to JIT all the code at run time; you should be able to cut the load time in half by compiling rspec and its dependencies, but that has a couple of caveats right now, you can read more about it in the README for my rubygems plugin:
https://github.com/ferrous26/rubygems-compile
Also, there are a couple of issues in the macruby trac related to slow gem loading time. You may wish to add a comment there about rspec.
Mark Rada
mrada@marketcircle.com
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel