Bagdevi, If you rename the par-packed executable to "b.exe", then running it as "b" should invoke the "b.pl" script. That is, the perl script that gets invoked depends on the name of the executable itself. You can achieve the same end on Unixen without renaming by using links; I am not sure if this works on Windows, but I would be curious to know. :-)
FYI, my information comes from a similar question <https://metacpan.org/pod/distribution/PAR/lib/PAR/Tutorial.pod#Aggregating-multiple-programs> posed in the Tutorial. Hope that helps! David On Tue, Jul 22, 2014 at 3:45 AM, Bagdevi <bagdevi.mis...@gmail.com> wrote: > Dear Group, > > I am trying to make a group of perl script, bundle up together to act > inside one executable. I know I can bundle up multiple perl script together > as follows. > > pp -o a.exe a.pl b.pl c.pl > > I can unzip the a.exe and see that a.pl, b.pl and c.pl are inside the > script/ folder. > > My problem is, I want to run b.pl and c.pl from inside a.pl. In the > script a.pl I have lines of code such as follows: > system ("perl b.pl" ); > system ("perl c.pl d 1>out 2>error"); > > And I want that I should be able to run b.pl and c.pl from a.pl, > according to what the user selects in the GUI. > > pp -o a.exe a.pl b.pl c.pl :did not work > pp -o a.exe a.pl -a b.pl -a c.pl :also did not work > > I tried to change the system commands in a.pl as follows: > > system ("perl script/b.pl" ); > system ("perl script/c.pl d 1>out 2>error"); > > This also does not work. > > Please suggest how to deal with it. > > Thanks a lots for your help and time, > > > Regards, > Bagdevi Mishra. > -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan
