There are many BAT files within QLIB to help you.

these are to compile programs to EXE files
  MASM2EXE.BAT - compile with MASM v6.11 (using ML.EXE)
  TASM2EXE.BAT - compile with TASM32.EXE (using TASM32.EXE)
  BC2EXE.BAT - compile with Borland C v4.5 (and v5.0) (using BCC32.EXE)
  WC2EXE.BAT - compile with Watcom C v10.6 (using WCC386.EXE)
  MC2EXE.BAT - compile with Microsoft Visual C++ v4.x (using CL.EXE)
  BCPP2EXE.BAT - compile with Borland C v4.5 (and v5.0) (using BCC32.EXE)
  WCPP2EXE.BAT - compile with Watcom C v10.6 (using WPP386.EXE)
  MCPP2EXE.BAT - compile with Microsoft Visual C++ v4.x (using CL.EXE)

these just create the OBJ file (no link):
  MASM2OBJ.BAT - compile with MASM v6.11
  TASM2OBJ.BAT - compile with TASM32.EXE
  BC2OBJ.BAT - compile with Borland C v4.5 (and v5.0)
  WC2OBJ.BAT - compile with Watcom C v10.6
  MC2OBJ.BAT - compile with Microsoft Visual C++ v4.x (using CL.EXE)
  BCPP2OBJ.BAT - compile with Borland C v4.5 (and v5.0)
  WCPP2OBJ.BAT - compile with Watcom C v10.6
  MCPP2OBJ.BAT - compile with Microsoft Visual C++ v4.x (using CL.EXE)

others
  QLINK.BAT - link multiply OBJ and LIBs together
  QMAKE.BAT - runs NMAKE
  BUG.BAT - invokes WD.EXE (watcom debugger) to debug a program
  QLITE.BAT - uses PMWLITE to compress an EXE file (giving it needed options)
  QSETUP.EXE - this works the same as PMWSETUP but has only 2 options to
             -  control how much memory QLIB will alloc on startup
             -  this is better than using the PMWSETUP because this will
             -  work under RAW,XMS,VCPI and DPMI unlike PMWSETUP.  But you'll
             -  still need to use PMWSETUP.
             - See qsetup.txt for more info

Notes:
  All xxx2exe.bat files use QLINK to link the final EXE.
  You can run each BAT file without any arguments to get help on that
    BAT files usage.
  The PMWSETUP utility is a great way to manage memory usage and such with
    your EXE files.  But if you have to run that each time you compile your
    project it can become a pain.  Fortunately my BAT files offer a relief.
    When linking is performed and if there is a .SET file with the same name
    as the EXE file to be compiled this SET file will be run as a BAT file
    which could run the PMWSETUP program or QSETUP or anything else you want.
    See \test\spawn.set to see what I mean.  To compile the spawn test
    program use "QMAKE SPAWN".
    This BAT file is run only once just before QLITE is used to compress
    the EXE (if the /c option was used).  The SET file used to be run
    twice but this is no longer the case.  One parameter is give to the
    SET BAT file and this is just the EXE filename. See also \test\ram.set
    for an example.
    The order in which QSETUP or PMWSETUP is used in SET files does
    not matter any longer.  Just note that QSETUP can not work on
    compressed EXEs so that is why SET files are run _before_ QLITE
    is used.

TTYL


