macruby_deploy gets the rubygems source code to actually look up the gem. You mentioned that you use RVM. Did you configure your GEM_PATH and GEM_HOME so that they point to the non-RVM places or were you just making the directories yourself?
Rubygems looks for its cache of gemspecs to find the gems, so if the directory layout in /Library/Frameworks/MacRuby.framework/Versions/0.9/usr/lib/ruby/Gems/1.9.2 is not what it expects then it will not find the gems. /Library/Frameworks/MacRuby.framework/Versions/0.9/usr/lib/ruby/Gems/1.9.2 should have these directories in it: cache/ doc/ gems/ specifications/ I think you only need the specifications and gems directory for things to work, but I am not sure. Mark Rada mr...@marketcircle.com On 2011-03-01, at 10:00 PM, Russ McBride wrote: > > oh, the command I'm using in my build script > > PATH="$PATH:/usr/local/bin" macruby_deploy --gem action_mailer > --embed "$TARGET_BUILD_DIR/$PROJECT_NAME.app" > _______________________________________________ > 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
