Just wanted to report from the field that gem packaging in the new
macruby_deploy is working great. It really simplified our build scripts. For
reference:
PATH="$PATH:/usr/local/bin" macruby_deploy --embed
"$TARGET_BUILD_DIR/Redwood.app" --gem nokogiri --gem gdata_19 --compile
Thanks for this hug
Thanks Mark. Yeah, that's what I've got. Under Versions, Current is linked to
0.9 inside of which is:usr/lib/ruby/Gems1.9.2/
This has:
cache/ doc/ gems/ specifications/
So it looks like it should work
On Mar 1, 2011, at 18:57 , Russ McBride wrote:
>
> I've stopped fighting with gems and just gave into the new --gem option in
> macruby_deploy today. Alas, I'm fighting with gems again.
>
> My app, which I'm adding features to, btw, has been running quite nicely here
> at UC Berkeley to driv
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 g
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.macosfo
I've stopped fighting with gems and just gave into the new --gem option in
macruby_deploy today. Alas, I'm fighting with gems again.
My app, which I'm adding features to, btw, has been running quite nicely here
at UC Berkeley to drive Selenium as a web app probing and monitoring device.
I'm g
