Non-portable configuration in the Windows distribution

Started by obetz, May 22, 2019, 02:08:29 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

obetz

May 22, 2019, 02:08:29 AM
Hi Phil,

pp adds installation specific configuration files from your Perl installation: Config.pm and Config_heafy.pl contain absolute paths to C:\Perl\. (many) and C:\MinGW\i686-w64-mingw32\... (several).

I don't know much when and where these entries are used, only one:

Perl tries to run $Config{sitelib}/sitecustomize.pl at startup, that's currently  "C:\Perl\site\lib\sitecustomize.pl".

Not many users will have such a script, but it shouldn't be used by ExifTool Windows.

Oliver

Phil Harvey

#1
June 07, 2019, 07:13:47 AM
Thanks for this note.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

obetz

#2
August 11, 2019, 11:41:23 AM
Quote from: obetz on May 22, 2019, 02:08:29 AM
Perl tries to run $Config{sitelib}/sitecustomize.pl at startup, that's currently  "C:\Perl\site\lib\sitecustomize.pl".

this was wrong, ExifTool's Perl does not try to run C:\Perl\site\lib\sitecustomize.pl on startup.

https://perldoc.perl.org/perlrun.html writes: "The value of $Config{sitelib} is also determined in C code and not read from Config.pm , which is not loaded."

Sorry for the wrong information.

Oliver
Print
Go Up Pages1
User actions