From: Erik Veenstra <erikveen@...>
Date: 2006-10-30T02:17:04+09:00
Subject: Re: Rubyscript2Exe directory management

> > Second, I can't "just extract" the app. I try running with
> > the --eee-just-extract flag and I get this: COuldn't create
> > directory c:\temp\C:/ApplicationDirectory

It's only possible to use a fixed directory name in %TEMP%. You
can't specify a full path. But it probably isn't too hard to
implement. I'll consider it.

> Ok, not really sure what changed on me, but I'm getting
> different results now. I can run --eee-justextract on my
> application and it does successfully explode itself into the
> current directory.

You did "--eee-justextract" instead of "--eee-just-extract"...
;] The former works; the latter doesn't.

> I could swear that it tried to extract itself into the temp
> directory yesterday, I did not imagine that nested C:\ error
> message :).

"c:\temp\C:/ApplicationDirectory" probably was a result of
running "--eee-just-extract" in combination with
"RUBYSCRIPT2EXE.tempdir='C:/ApplicationDirectory'". Debugging
isn't easy when making 2 errors at the same time... ;]

> > where c:\ApplicationDirectory is what my present working
> > directory was when I ran the original rubyscript2exe
> > executable.

Sorry, should be "3 errors"... ;] You probably thought that
"c:\ApplicationDirectory" was there because it was the current
directory, although it probably was there because you specified
it in your code. But I'm not sure, it's just a guess.

> I am specifying the -I lib\ parameter, as described in the
> instructions:
>
>   bin\ruby -I lib\ app\init.rb

That's not correct, anymore. (As usual, code is faster than
documentation...) It should be (on Windows):

 bin\ruby -r .\bootstrap.rb -T1 empty.rb .\app\yourscript.rb

This bootstrap.rb sets up the (fake) RubyGems environment.

Thanks.

gegroet,
Erik V. - http://www.erikveen.dds.nl/