There's more than one way to do things | |
PerlMonks |
Re: POE & Tk totally confound perlapp (or am I missing something?)by Marshall (Canon) |
on Apr 18, 2009 at 03:42 UTC ( [id://758394]=note: print w/replies, xml ) | Need Help?? |
I haven't used POE, but have built a number of Tk apps in .exe form using ActiveState. I don't mess around with manually editing the --add command line stuff. I put explicit "use" statements in the code. In the case of Tk, although just "use Tk;" is enough when running in normal environment, to make the .exe I find that I need to "use" all of the individual widgets that the program calls...like below.. You may find that "using" the module in the code produces a different result than --add does. Your mileage may vary, but I would suggest trying this approach.
UPDATE: I looked at one of my .PerlApp files. Now I am on 7.1 and haven't installed the latest version yet...BUT this is a real product in its 2nd year of production. The project code name is "green" which of course means nothing to you. I took out some path names, but this is basically what your .PerlApp file should look like. Notice: this .exe is not dependent on anything, there are no dynamic .dlls's, AND nothing has been "forced" into the .exe. This Gui: 0 stuff means that there is a command window that starts also (ie, this is not a strictly GUI only application). Hostname "bigmomma" is just the name of my build machine. Your .PerlApp file should look like this...very clean...no voo-doo. As far as path goes, in the PerlApp application, C:\Perl\site\lib;C:\Perl\lib;. In other words, this builds from the standard libraries and accesses current directory for non_standard ones (they could be in a different directory). Hope this helps! When your .PerlApp file looks as clean as this, you will have a working .exe file.
In Section
Seekers of Perl Wisdom
|
|