Re^2: finding perl58.dll

[rvosa]

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?

[Anonymous Monk]

PAR uses Module::ScanDeps

[rvosa]

But not to find the dll, I don't think? I thought M::SD only works on text files?

[syphilis]

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