Thanks Mark! thats it: script: $0 = /Volumes/KanDriv/svn_repos/alpha/trunk/perl/svn_tools/testDir.pl $^X = /usr/bin/perl
with pp: $0 = /Volumes/KanDriv/svn_repos/alpha/trunk/perl/svn_tools/testDir_pp $^X = perl with PerlApp: $0 = /Volumes/KanDriv/svn_repos/alpha/trunk/perl/svn_tools/testDir_perlapp $^X = perl so that happen to be the most portable way of doing it, this way I don't have to modify my programs to package them with either utility. l-p [EMAIL PROTECTED] wrote ---- Hi, from memory, $0 contains the full path to your exec when packaged. Try packaging print qq(\$0 = $0\n); print qq(\$^X = $^X\n); and see what it gives you. This should mean that $0 should always work in packaged code if it worked in the script. (I think !!!) Regards Mark Louis-Philippe wrote: > Hi All, > > I am new to PAR & pp, I discovered it this week when I ran into trouble > trying to package scripts with PerlApp that PerlApp wouln't package because > of version compatibility... so I tried pp an just felt in love with is > simplicity & free nature. > > so, now I am trying to port my script to pp, and one command is missing from > my toolkit: > in PerlApp, I am aple to call PerlApp::exe() to get the executable file > directory, > something I would do with cwd() inside of a straight .pl script... > I tried cwd() with a pp executable and it returns the shell working directory > (i.e. my home folder). > anybody knows how to grab the executable directory path with pp? > > thanks! > > l-p
