From: Brian Wallace <draygen80@...>
Date: 2009-04-03T23:53:43+09:00
Subject: Re: RubyScript2Exe

--0015174c368ec919940466a7b8b5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I've been using rubyscript2exe with 1.8.7 without any problems.

I've tested it in Vista + XP ... It uses an "eee" wrapper for the executabl=
e
.. You'll find that when you run an exe compiled by rubyscript2exe, it
extracts all of the files into:

\Documents and Settings\<username>\eee\

There is an option to just extract the files from Rubyscript2exe and not ru=
n
the .RB, I would extract the files, and make sure your application runs via
"ruby scriptname.rb" in the directory that it extracts to.

The argument to pass to your compiled exe is --eee-just-extract.

On Fri, Apr 3, 2009 at 9:21 AM, Charlie Openshaw <
charlieopenshaw@hotmail.com> wrote:

> Lars,
>
> Thanks for taking the time to help me.
>
> As I mentioned in my original post I've managed to get this to work
> before but for some reason I can't get the exe working anymore.
>
> It says it's supported up to version 1.8, and I've got 1.8.26, so would
> it be best to just install version 1.8 of Ruby?
>
> Charlie
>
>
> Lars Christensen wrote:
> > On Thu, Apr 2, 2009 at 4:49 PM, Charlie Openshaw
> > <charlieopenshaw@hotmail.com> wrote:
> >> Hi,
> >>
> >> I am a complete novice to ruby, so please feel free to ask for more
> >> information so this post makes more sense.
> >>
> >> I am trying to create an exe from the ruby script, and it all seems to
> >> go well but the resulting exe doesn't do what it's supposed to. =EF=BF=
=BDWell it
> >> doesn't do anything at all in fact!
> >
> > I had a quick look at rubyscript2exe yesterday. It's not currently
> > maintained and is not compatible with current versions of Ruby (throws
> > exceptions with 1.8.6p287). I would not recommend it for use in its
> > current state.
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

--0015174c368ec919940466a7b8b5--