Re: [Rubycocoa-talk] RubyCocoa macosx bundle without installed ruby ?

[Jonathan P. <jp...@dc...>]

On 22 Apr 2005, at 20:18, Remo Eichenberger wrote:

> i'm very interest on this script. i'm also interest about how it 
> works. i'm very happy when you can post this :)

I've attached the script to this message.

It still needs work, but hopefully some people will find it useful and 
it can be improved.

Except from the header:

# standaloneify.rb
# Takes a built RubyCocoa app bundle (as produced by the
# Xcode/ProjectBuilder template) and copies it into a new
# app bundle that has all dependencies resolved.
#
# usage:
#   ruby standaloneify.rb -d mystandaloneprog.app mybuiltprog.app
#
# This creates a new application that should have dependencies resolved.
#
# The script attempts to identify dependencies by running the program
# without OSX.NSApplicationMain, then grabbing the list of loaded
# ruby scripts and extensions. This means that only the libraries that
# you 'require' are bundled.
#
# NOTES:
#
#  Your ruby installation MUST NOT be the standard Panther install -
#  the script depends on ruby libraries being in non-standard paths to
#  work.
#
#  I've only tested it with a DarwinPorts install of ruby 1.8.2.
#
#  Extension modules should be copied over correctly.
#
#  Ruby gems that are used are copied over in their entirety (thanks to 
some
#  ideas borrowed from rubyscript2exe)
#
#  install_name_tool is used to rewrite dyld load paths - this may not 
work
#  depending on how your libraries have been compiled. I've not had any
#  issues with it yet though.