in reply to Re: PerlApp can't find bound module
in thread PerlApp can't find bound module
As the Op gains more experience in writing Perl code destined for PerlApp compilation, the simplicity and efficiency of adding "use" statements to the source code rather than PerlApp option statements at the compilation phase to force inclusion of a module that the dependency checker doesn't think should be there will become apparent.
I strongly recommend writing source code that is easy for the dependency checker to deal with. When there are 2 sets of double colons, this almost a sure bet that a "use" statement will be needed and I just add that into the source code as I write it. Also, there are other ways of making a .exe file from Perl code rather than PerlApp, and those "other ways" will understand what to do when they see a "use" statement. My goal is that the source code "speaks for itself" and that is possible with Perl.
|
|---|