From: Sean Middleditch <elanthis@...>
Date: 2001-10-02T03:37:10+09:00
Subject: [ruby-talk:21884] Re: Ruby2Exe

On Mon, 2001-10-01 at 14:24, Gil Cohen wrote:
> Okay, here goes:
> 1. It automagically compiles, it runs the gcc command for the C file
> that's created.
> 

Nifty.  ^,^

> 2. Right now it only works on Linux, although I'm quite sure it can be
> made to work in a cygwin environment with very few/no changes
> whatsoever.
> 

That would be cool.  Ruby doesn't work with VC++?  Otherwise you have to
distribute all sorts of compatibility libraries...

> 3. Command line flags, not yet. I'm pretty sure that environment
> variables are passed perfectly. ( Can't test it right now, though. )
> 

Alright.

> 4. It handles C extensions perfectly, but you have to give the full path
> to the extension in the Ruby source file, and even then, the C extension
> isn't embedded in the executable. 
> 

Ew.  ~,^  That'll make portability a pain until improved.  

> 5. It's not wishful thinking, it will happen, eventually :)
> 

Cool.  ^,^  Out of curiosity, are you planning on keeping this in Perl,
or rewriting in Ruby?  I understand that some languages are bettre
suited to certain tasks, but it would be a great proof of Ruby's
systems-level ability.  Besides, if this is ported to Windows, it won't
do any of the 3 machines I have around here any good, since they only
have Python and Ruby on them

Sean Etc.

> Signed,
> Gil
> 
> -----Original Message-----
> From: Sean Middleditch [mailto:elanthis@awesomeplay.com] 
> Sent: Monday, October 01, 2001 2:04 PM
> To: ruby-talk ML
> Subject: [ruby-talk:21882] Re: Ruby2Exe
> 
> That's cool.  I don't have time to look over things now (yet I have time
> to sit here and read e-mail, so I'm a contradiction, :P) so I was
> wondering, does this just convert to a C file?  Does the utility
> automatically compile, as well?  On what platforms does this work?  On
> UNIX I see little point in this script, but I see lots of use in Windows
> where people are used to running software this way.  Some code to
> automatically cross compile when on a UNIX/Linux box would be nice too,
> so I could compile and send to my Windows-using coworkers.
> 
> Also, does the resulting executable properly handle all the proper
> command line flags and environment vars and such?  It would also be nice
> to be able to tell the script alternate directories for module files.
> 
> Finally, will it handle C extensions properly?  I imagine that there
> would be some need for either a static library for the source for the
> extension, but if it could be found, that would be a really spiffy
> feature.  ^,^  But I think that's wishful thinking...
> 
> Sean Etc.
> 
> On Mon, 2001-10-01 at 13:43, Gil Cohen wrote:
> > It does need the environment for the time being, tonight, I'll add in
> > support for reading the require '' lines, and staticly linking the
> > require lines, as well as the ruby interpreter into the resulting
> > executable.
> > 
> > Signed,
> > Gil
> > 
> > -----Original Message-----
> > From: Sean Middleditch [mailto:elanthis@awesomeplay.com] 
> > Sent: Monday, October 01, 2001 1:41 PM
> > To: ruby-talk ML
> > Subject: [ruby-talk:21880] Re:
> > 
> > What?  You didn't write the script in Ruby, but in Perl?  ~,^
> > 
> > Still, this is rather interesting.  Similar to Python's freeze.  Does
> > the resulting executable need a Ruby environment to run (i.e. does it
> > need external modules to be installed, or will it automatically fold
> > those into the resulting executable if it can determine which are to
> be
> > loaded?)
> > 
> > Sean Etc.
> > 
> > On Mon, 2001-10-01 at 13:29, Gil Cohen wrote:
> > > Dear All,
> > > 
> > > Yesterday I wrote a simple perl script that converts Ruby programs
> to
> > C
> > > (it's actually, pretty simple. It just does a simple XOR encryption
> on
> > > the script, and uses rb_eval_string to run it) Nonetheless, it still
> > > works.
> > > 
> > > http://sung.lostgeeks.net/ruby2exe
> > > 
> > > 
> > > Signed,
> > > Gil
> > > 
> > 
> > 
> > 
> 
> 
>