Consider yourself my hero Mark.
Oddly, they appear in the bundle uncompiled, but with their extensions back on
=]
Thanks for the help.
--
Stephen Horne
On 21/06/2012 at 12:02, Mark Villacampa wrote:
> I'm going to risk this being a stupid answer, but have you tried deleting the
> file
I'm going to risk this being a stupid answer, but have you tried deleting the
file extension? That way MacRuby will not compile those files, and you might
still be able to execute those scripts they way you need them.
--
Mark Villacampa
Twitter: @MarkVillacampa
On Thursday, June 21, 2012 at
Hey Josh,
I think this is where I'm getting lost - I can't see a macruby_deploy phase
anywhere.
I'm clicking on the project icon above all the files in the project navigator,
then clicking on the target, then 'Build Phases', and the final phase is 'Copy
Bundle Resources'.
I tried adding an
Hey Stephen,
You will need to create a new "Move Files" phase (can't remember the exact name
at the moment…) after the macruby_deploy phase. The macruby_deploy script will
attempt to compile any *.rb file it finds under your project, which is why
you're seeing this.
Cheers,
Josh
On Wednes
I have a collection of scripts that I want to call from my application. These
are 1.8.7 ruby scripts, and cannot be converted to MacRuby.
Currently, I have them installed in a separate directory, and I just call them
from the application.
I would like to place them within the bundle to keep eve
