From: ptkwt@...1.aracnet.com (Phil Tomson)
Date: 2002-09-07T04:32:10+09:00
Subject: Re: OS-independent build of ruby

In article <alali7$cth$01$1@news.t-online.com>,
reckless <reckless2k@yahoo.com> wrote:
>Hi,
>
>I need a version of ruby that I can bind / extend with OS-independent C++
>classes; I only need the basic script functionality (variables, control
>loops, etc.), most of the logic will exist in the C++ system classes.  SWIG
>is attractive, if it works, 

Swig does work well and it's getting better all the time.


> but I still need an OS-independent executable of
>the ruby interpreter.
>

Uhhhh....  That's a tall (many would say impossible) order... Maybe you 
should look at JRuby which targets ruby to the Java Virtual Machine, but 
I'm not sure that's what you're looking for.

>At the moment, I am developing under windows, but this is not the target
>platform.  What is the best way to proceed?
>

Not sure why you think you need "OS-independent executable of the ruby 
interpreter".  Most Ruby code itself will be portable (except where you 
might be calling OS dependent libraries - If you're doing that then it's 
best to 'abstract' those calls and put the OS dependent stuff into some 
modules that can be mixed-in depending on the OS you're running on [which 
can be determined at run-time] ).

Phil