From: Craig W. <cwi...@ma...> - 2008-06-11 14:39:44
|
On Jun 11, 2008, at 8:22 AM, Allison Newman wrote: > Craig, > > I think you may have misunderstood me, or perhaps misunderstood what > a gem actually is. Anyway, I'll try to clarify. My current app > doesn't use gems, because I don't have need of any of the > functionality that gems give. If I've understood you correctly, you > wish to use sqlite, and hence need a gem to do this. > > In the Ruby world, gems are libraries that are installed into a > specific folder on your computer, using the gem command line tool. > This folder is NOT inside your application - it is globally > accessible by all Ruby apps on your computer. Unfortunately for > you, if you use the gem in your app, your app will no longer work on > another computer that does not have the gem installed. > > Fortunately for you, the gurus that created RubyCocoa have created a > tool called standaloneify.rb that Eloy keeps talking about. This > tool goes your code, identifies all libraries that your app depends > on, and copies them into the Resources folder of a new, standalone, > version of your app. It really is very simple to use - using > Terminal, simply cd to the folder containing your app, and run the > command: > > ruby standalonify.rb -d MyStandaloneProg.app MyBuiltinProg.app > > changing the names for your original app, and it's standalone > version, evidently. > > The link that Eloy gave you explains all of this pretty clearly (or > at least I personally find it very clear, your mileage may > vary :-) ). I think it really is going to be the simplest solution > for you. > > Hope that helps. > > Alli > That helps alot! Thank you both for the explanation. I have standalonify.rb exactly where Eloy point to but when I run the code above I get the following error: ruby standalonify.rb -d ScriptWindow_.app ScriptWindow.app ruby: No such file or directory -- standalonify.rb (LoadError) I am in the directory where the app resides before running above code. Craig |