in reply to Perl2exe bug!
I don't use Perl2exe, but it might be that your version of it (has an error|is outdated).
Might I also suggest against using Perl2exe unless you really have to. Even something like installing Perl on 58 Windows machines so your client-server script can run calls for the installation of something like ActiveState Perl on the aforementioned machines. The perl-to-exec compilers aren't that great/reliable, and it's best to keep your code as-is so that it can change with the times.
Considering the inclusion of the Tk modules, your program (after compiling) will be somewhat large.
If you are using Perl2exe to "protect" your source, Perl2exe offers a false sense of security. If your code is under a strict license, I advise shipping it encrypted and having a subroutine that reports back to you with registered information, just to keep things legal.
Opinions may differ, but I see no practical application where Perl2exe is necessary.
Perl2exe can also cause its on headaches, like the one you encountered, and the little registration hassle it imposes on Unix machines.
Try redownloading Perl2exe, after finding the most current version. If you wouldn't mind, could you elaborate on what you are using it for? Perlhaps there's a better method.
Hope this helps.
John J Reiser
newrisedesigns.com
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Perl2exe bug!
by dimmesdale (Friar) on Jun 26, 2002 at 12:29 UTC |