Re: [Rubycocoa-talk] packaging ruby within an RC app

[Jon B. <jo...@gm...>]

Going to guess its just a static library build of ruby itself ...

[MacBook-Pro:/opt/local/lib]$ ls *ruby*
libruby-static.a        libruby.1.8.6.dylib     libruby. 
1.8.dylib       libruby.dylib

I know there are a few way you can compile/build the ruby binary  
itself ...

[MacBook-Pro:~/ruby-1.8.6]$ ./configure --help | grep static
   --with-static-linked-ext link external modules statically
[MacBook-Pro:~/ruby-1.8.6]$ ./configure --help | grep shared
   --sharedstatedir=DIR   modifiable architecture-independent data  
[PREFIX/com]
   --enable-shared         build a shared library for Ruby.
[MacBook-Pro:~/ruby-1.8.6]$

If you were super picky you could probably build it + bundle w/ only  
packages you really need (I have run ruby on a Zaurus before).  But I  
know just from looking that Slingshot comes w/ the kitchen sink.

Seems to have come up on lists before (a Slim Ruby) ...
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-list/41452

- Jon

On Jul 10, 2007, at 9:40 AM, Tim Perrett wrote:

> Ok thats interesting - however in his 'lib' dir he has  nkf.bundle,
> stringio.bundle, strscan.bundle  - which I dont think you are talking
> about. There is no such directoy as ./Resources/lib so you must
> mean ../lib?
>
> Looking at the rb_main, those other bits have been added by
> standalonify - looking in standalonify.rb in the src, you can see
> exactly the same as what is in PackRat. I understand what you are
> getting at however, and it makes sense :)
>
> I am still iterated as to how Slingshot have it working, as that
> seems like it would be a very elegant solution? There code base is
> much more tidy than that of locomotive. What does the static.a  
> thing do?
>
> Cheers
>
> Tim
>
>
>
> On 10 Jul 2007, at 14:19, Jon Baer wrote:
>
>> You know what is a good app to check out ...
>>
>> http://infinitenil.com/packrat/
>>
>> Download it and jump into /Applications/PackRat.app/Contents/
>> Resources and take a look @ how his "lib" and rb_main.rb are laid
>> out.  I found it be pretty helpful, although still not sure if it
>> was all generated by standalonify + if this is the "standard" way
>> to do it.
>>
>> In a nutshell (just remember to load REXML first):
>> COCOA_APP_RESOURCES_DIR = File.dirname(__FILE__)
>> $LOAD_PATH.reject! { |d| d.index(File.dirname
>> (COCOA_APP_RESOURCES_DIR))!=0 }
>> $LOAD_PATH << File.join(COCOA_APP_RESOURCES_DIR,"ThirdParty")
>> $LOAD_PATH << File.join(File.dirname(COCOA_APP_RESOURCES_DIR),"lib")
>> $LOADED_FEATURES << "rubycocoa.bundle"
>> ENV['GEM_HOME'] = ENV['GEM_PATH'] = File.join
>> (COCOA_APP_RESOURCES_DIR,"RubyGems")
>>
>> HTH,
>>
>> - Jon
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk