Hi, I've temporarily put the following two files on my website for download:
http://www.hoppfrosch.de/temp/test.par http://www.hoppfrosch.de/temp/test_par.pl This combination generates the described behaviour. One more observation I made: Generating the par-file without Option -B (pp --lib D:\lib -p -o test.par test.pl) shows a different behaviour with my test script: #perl.exe -w use strict; use PAR; use lib "test"; use Version::BuildmachineVersion; print Version::BuildmachineVersion::getCompleteVersionString(); exit 1; The line print Version::BuildmachineVersion::getCompleteVersionString(); is executed, but the exit statement isn't reached - The script runs "forever". Using the "-B" option the print-statement isn't executed at all ... Johannes IvorW schrieb: > >> -----Original Message----- >> From: Johannes Kilian [mailto:[EMAIL PROTECTED] >> Sent: 04 January 2007 12:45 >> To: [email protected] >> Subject: [Question] Generating and Using PAR-Files >> >> Hi there, >> >> I used to use PP to bundle a few perl programs into >> standalone executables - and everything works fine. >> >> Now I'm playing around with bundling modules and all >> dependencies into a *.par file and using this par file from >> my Perl-Skripts. >> My question is probably a beginners question - but I cannot >> figure it out yet. >> >> I'm using the latest versions of PAR (0.970) - I've dowloaded >> it from CPAN and installed it on my machine (WINXP SP2, >> VC6-Compiler, ActivePerl 5.8.8). >> >> I use the following command-line to generate my PAR-File: >> pp -B --lib D:\lib -p -o test.par test.pl >> >> My dependencies and lib directory are quite large (about 100 >> own modules in D:\lib) - so the resulting PAR File is about >> 5.0MB large. >> Trying to use the PP-generated PAR-file from a perl script >> fails: The script starts - but runs forever. >> ------ >> #perl.exe -w >> use strict; >> use PAR; >> use lib "test"; >> use Version::BuildmachineVersion; >> print Version::BuildmachineVersion::getCompleteVersionString(); >> exit 1; >> ------- >> (This is just a very simple example script) >> >> Building a separate PAR-file by hand, using ZIP and packing >> only my files from D:\lib into the PAR-File everything works >> as expected. (all other dependencies are installed on my machine ...) >> >> My script test.pl - used to generate the par via pp - mostly >> contains "use" directives to force pp to put all my desired >> Modules into the par-file ... >> >> What's wrong with the pp-generated par-file? >> How do I correctly build a PAR-File using PP which can be >> used as library? >> (The par file should contain all it's dependencies, since it >> has to run on a external machine) >> >> >> Any help welcome >> >> Johannes >> >> > Can you please attach (or host) a minimal .par file that illustrates the > problem. Perhaps a "hello world" that uses and checks for a few modules. > >
