Files
mercury/scripts/mercury.bat.in
Julien Fischer f7921d7b47 Fix a problem using mdb from cmd.exe on Windows.
More generally, clean-up the various batch files we have.

scripts/mdb.bat.in:
    Ensure that the value of MERCURY_DEBUGGER_INIT environment variable does
    *not* include double quotes, otherwise the path to the mdbrc file will
    be incorrect.

scripts/*.bat.in:
    Require command extensions to be enabled. This is the default on
    all Windows systems we support; explicitly enabling them is just in case
    the user turns them off for some reason.

    Don't disable echoing twice.

    Quote the entire argument to the set command; this should avoid double
    quotes ending up where we don't want them.

    Update copyright notices.
2024-01-12 18:19:21 +11:00

28 lines
1.1 KiB
Batchfile

@echo off
rem @configure_input@
rem ---------------------------------------------------------------------------
rem Copyright (C) 2001, 2003, 2005, 2011 The University of Melbourne.
rem Copyright (C) 2020, 2024 The Mercury team.
rem This file may only be copied under the terms of the GNU General
rem Public License - see the file COPYING in the Mercury distribution.
rem ---------------------------------------------------------------------------
rem
rem mercury.bat - Melbourne Mercury Compiler.
rem
rem Use `mercury -h' for help.
rem
rem ---------------------------------------------------------------------------
rem This is a Windows batch file version of the `mmc' Bourne shell script.
rem (We don't use that name because it conflicts with that of the Microsoft
rem Management Console.)
rem ---------------------------------------------------------------------------
rem Do not export any local environment changes and ensure command extensions
rem are enabled.
setlocal enableextensions
set "MERCURY_CONFIG_DIR=@CONFIG_LIBDIR@"
set "MERCURY_COMPILER=@PREFIX@\bin\mercury_compile"
%MERCURY_COMPILER% %*