[Tex/LaTex] nyway to configure MiKTeX so that it locates script engine perl.exe

latexmkmiktex

I am using MiKTeX and I keep receiving the following error from latexmk.exe even if I have done all the necessary actions to handle this: Downloaded latexmk 4.48, created a folder scripts\latexmk\perl, copied latexmk.bat & latexmk.pl in it and added in latexmk.bat the full path of the perl.exe in my PC)

Unfortunately, the error message does not indicate where is latexmk.exe looking for the perl engine — big S/W flaw! So, how can I find where is MiKTeX looking for this script engine so that I can either move latexmk.bat & latexmk.pl in there or configure MiKTeX to look for the necessary files in scripts\latexmk\perl ?

(Added later)
Here are the 2 error message lines:

latexmk: The script engine could not be found.

latexmk: Data: scriptEngine="perl.exe"

(Note: I have also tried using the parent folder: scripts\latexmk. No luck! All the scripts are there. Where else is MiKTeX looking for latexmk.pl???)

Best Answer

I found that the path of perl.exe must be in environment PATH. This is the only way I could make MiKTeX's tatexmk.exe run.

So, the answer to the question is that MiKTeX is not configuarable as far as this issue is concerned.

Related Solutions

[Tex/LaTex] How to make the perl script [makeglossaries] work on WinXP

You need to install Perl. There's a free version for Windows: ActivePerl Community Edition.

To debug, don't start with the editor but

Check if makeindex works at all, run it yourself
Test the Perl script
Test the batch script
Now you could test the editor integration

[Tex/LaTex] MiKTeX and Perl scripts (and one Python script)

A definitive solution could only be given by Christian Schenk, the developer of MiKTeX. I am like most others just a simple user without knowledge in reading the MiKTEX sources. But nevertheless from empiric experience I guess he removed intentionally the rudimentary Perl included in earlier versions (as already said in question: my memory can deceive me), so it’s one thing less, he has to keep up to date. In this case the real issue would be, that this seems nowhere to be mentioned in official MiKTeX documents or on MiKTeX.org (again: mistakes on my side are possible).

So, what can be done then?

^{I will only describe the approach for Perl, but for Python it is analogical. Download overview in Python for Windows.}

The answer is: Install a full Perl distribution on your own!

You can find links to Windows versions of Perl distributions on Perl.org download page.

If you have no idea, which one to choose, I suggest you to install ActivePerl by ActiveState. There’s a “Free Community Edition” installer (at time of writing do not download the latest version, but the recommended one, because otherwise you cannot add perl repositories for module updating). By default a package manager is also installed which is later useful for updates and configuration.
For advanced users there’s also Strawberry Perl for Windows. The configuration is later done with command prompt terminals.
Both installers add the Perl interpreter to the system PATH environment variable and link the file extension .pl to the interpreter binary perl.exe, so it would generally be enough to start with click on the file or in command prompt typing in the file alone - but this does not work for files without extension (but perl file would work then).^*)
I cannot say anything about the third mentioned distribution DWIM Perl for Windows, but since it is claimed to be Strawberry based, it will be very similar.

^*) (One could even go further and add the file extension to system variable PATHEXT, see How do I make my Perl scripts act like normal programs on Windows?) for more.

But what to do, when Perl is installed, and even though still errors appear?

Sometimes the error is caused by another issue. Back in past almost every time the reason was, that a script path had changed, but the developer had forgotten to adjust the entry in scripts.ini. You cannot edit the file, as this would break functioning at all! (The file is signed.) But in such a case you can do the following. I’ll take latexdiff as example, where this once really happened.

Make sure you have created a local root directory, cf. Create a local texmf tree in MiKTeX. We will only need the bin subfolder here for what we want. You could also use another folder. That is in the system path, though, but mind the point, that it must be found before the MiKTeX binaries folder.

Start your favorite text editor and paste in the following lines. Of course, adjust the path to your installation, for the exact script path and name you have to look yourself:

@echo off & setlocal

:: Adjust path to MiKTeX root here, do not remove
:: the double quotes, when you have spaces in path!
:: By default in a 32-bit machine:
:: set MiKTeXPath="C:\Program Files\MiKTeX 2.9"
set MiKTeXPath="<Path-to-MiKTeX>"

perl %MiKTeXPath%\scripts\latexdiff\latexdiff %*

The last line would be different for texdef:

perl %MiKTeXPath%\scripts\texdef\perl\texdef.pl %*

You could remove the lines with double-colons in the beginning.

Save as text file in the binaries folder mentioned in item 1 above with the name as it appears before the equal sign in scripts.ini and the file extension .bat (or .cmd if you like this more), so in the example latexdiff.bat. Windows’ own Notepad is notorious for adding the extension .txt automatically. You can avoid this, when you save the file with double quotes: "latexdiff.bat".
Do a test: open the command prompt and type in latexdiff --version or latexdiff --help. When you get no output from your Perl script, then you must check whether you have typed the correct script path and name, and the binary folder with the batch file is found before the MiKTeX bin folder. The file extension is omitted, because the real calls are also made without it.
From time to time you should test, whether the function in MiKTeX was repaired. You can do this with typing explicitly the .exe wrapper version: latexdiff.exe --version. If successful you can delete the batch file then.

Best Answer

Related Solutions

[Tex/LaTex] How to make the perl script [makeglossaries] work on WinXP

[Tex/LaTex] MiKTeX and Perl scripts (and one Python script)

Related Question