I think that macgem should just compile the gem source files during
installation, by default. We could eventually add a --no-compile argument to
skip the compilation.
There is just one problem: AOT compilation does not remember the DWARF metadata
yet, so backtraces won't be complete. This is th
Hey Mark,
I agree with Matt that macruby_deploy needs work in this area, and any
effort you can contribute (or experience that you have gained from working
on your gem plugin) would be greatly appreciated. That said, I think a gem
plugin is a separate (and, IMHO at least, as valuable) issue.
So t
You're right; I don't want to use rubygems in a desktop app, I don't think that
is the purpose of Rubygems and is not a good use case. Rubygems is still quite
useful when I want to write a quick script that uses a gem, or when I simply
want to experiment with a gem in irb, which is one case for
Hey Mark, I think this is an interesting concept but I would encourage you to
work on the macruby deploy tool instead. The reason why I'm saying that is that
you probably don't wantto use rubygems in a desktop app, instead you probably
want to unpack a gem and it's deps in the app you ship.
Trun
Hey,
I recently wrote a small plugin for rubygems that will use the MacRuby compiler
to compile *.rb files when you install a gem.
It is usable, but very simple right now; I would like to make it more powerful
in a few different ways and I'm not sure which would be good. Things I think I
could
