Fix #79146: cscript can fail to run on some systems

In the buildconf and configure batch files, Windows' cscript utility was being
run without the /e:jscript flag. This works on systems that have not had the
default .js file association changed, but if .js has been re-associated to
(say) an IDE, the batch files fail with the error message:

Input Error: There is no script engine for file extension ".js".
This commit is contained in:
Deus Kane 2020-01-20 16:16:01 +00:00 committed by Christoph M. Becker
parent b67fc51859
commit 3046e35718
7 changed files with 7 additions and 6 deletions

View file

@ -352,7 +352,7 @@ function conf_process_args()
var i, j;
var configure_help_mode = false;
var analyzed = false;
var nice = "cscript /nologo configure.js ";
var nice = "cscript /nologo /e:jscript configure.js ";
var disable_all = false;
args = WScript.Arguments;