in reply to Re: perl, Tk GUI, problem with getOpenFile, in a packed program
in thread perl, Tk GUI, problem with getOpenFile, in a packed program

That isn't normally required with PAR/pp
  • Comment on Re^2: perl, Tk GUI, problem with getOpenFile, in a packed program

Replies are listed 'Best First'.
Problem solved. Many thanks!
by gbertrand (Initiate) on Jul 23, 2009 at 12:27 UTC
    The problem is solved!

    I have added several "use" statements explicitly to be sure that they would be packed within the binary. I have also changed the pp options that I used, which were probably wrong. I am not quite sure of the origin of my problem, but anyway, it's solved.

    Many thanks for your help.

      Great! Glad that you got things working!

      My client apps are sent out as .exe files with ActiveState tools. Server side is source code. There is a huge skill difference between the sys admin with /root access on Unix and some average Windows user! The .exe file for the Windows users is a very good way to go!

      Some folks don't believe that sometimes extra "use" statements are necessary when making these .exe files, but I have found that to be the case. I guess this is a "your mileage may vary situation". I will add that say "use Tk::Button;" is not going to "hurt" if you are actually using a Button...it won't slow the compile down or cause multiple copies of Tk::Button to be loaded or even compiled (Perl keeps track and only "uses" a module once).

      anyway congrats on your sucess...sometimes some experimentation and some "fiddling" is required!