laziness, impatience, and hubris | |
PerlMonks |
Re^3: POE & Tk totally confound perlapp (or am I missing something?)by rcaputo (Chaplain) |
on Apr 18, 2009 at 00:07 UTC ( [id://758380]=note: print w/replies, xml ) | Need Help?? |
That seems helpful. You should definitely not include POE::Loop::Select, since it's mutually exclusive of POE::Loop::TkActiveState. Can you force PerlApp to exclude modules? It may be that perlapp is too aggressive about including modules it finds in the source code, including POE::Loop::Select when it shouldn't be used. perlapp's output includes a number of errors, many of them within Tk. For example:
That shouldn't be an issue on Windows, which uses a case-insensitive filesystem. I don't know whether it's significant for PerlApp, though. Maybe we can narrow this down to a POE issue vs. a Tk issue? Have you tried bundling up a program that uses POE by itself? Have you tried bundling up a Tk program that doesn't use POE? Do they work separately?
In Section
Seekers of Perl Wisdom
|
|