Re^2: finding perl58.dll

Thanks for those replies! I was a bit unclear in my initial post, I think, though. I was wondering if there is a more general way to figure out where the $Config{libperl} lives that the running perl interpreter needs/is using. For example, how does PAR figure that out?

Comment on Re^2: finding perl58.dll

Replies are listed 'Best First'.
Re^3: finding perl58.dll by Anonymous Monk on Aug 29, 2006 at 05:36 UTC
PAR uses Module::ScanDeps	[reply]
Re^4: finding perl58.dll by rvosa (Curate) on Aug 29, 2006 at 06:03 UTC
But not to find the dll, I don't think? I thought M::SD only works on text files?	[reply]
Re^3: finding perl58.dll by syphilis (Archbishop) on Aug 30, 2006 at 01:20 UTC
I was wondering if there is a more general way to figure out where the $Config{libperl} lives I think the following would always produce the correct path on Win32 to $Config{libperl}: perl -MConfig -e "print $Config::Config{archlib}.'\\CORE\\'.$Config::Config{libperl}" Works for me - and on Linux if rewritten (with corrections to the directory path separator) as: perl -MConfig -e 'print $Config::Config{archlib}."/CORE/".$Config::Config{libperl}' Attend to the path separator issue (if that's applicable to your needs) and you should be able to come up with a truly portable script. Cheers, Rob	[reply]