There are many BAT files within QLIB to help you.

these are to compile single file programs to EXE files
  MASM2EXE.BAT - compile with MASM v6.11 (using ML.EXE)
  TASM2EXE.BAT - compile with TASM32.EXE (using TASM32.EXE)
  WC2EXE.BAT - compile with Watcom C v10.6 (using WCC386.EXE)
  BC2EXE.BAT - compile with Borland C v4.5 (and v5.0) (using BCC32.EXE)
  WCPP2EXE.BAT - compile with Watcom C v10.6 (using WPP386.EXE)

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

this is for larger projects
  QLINK.BAT - link multiply OBJ and LIBs together

this is for debugging
  BUG.BAT - invokes WD.EXE (watcom debugger) to debug a program

this is to compress EXE files
  QLITE.BAT - uses PMWLITE to compress an EXE file (giving it needed options)

this program is a setup utility for QLIB
  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.
             - See qsetup.txt for more info

You can run each BAT file without any arguments to get help on that
BAT file usage is.  Most are run the same way.  QLINK is when you need to
link together multiple OBJ and LIB files together.  QLINK still adds the
default LIBs and startup code used in the *2EXE.BAT does.

Notes:
  All xxx2EXE.BAT files use Borland Compatiable Math LIBs except WC2EXE.BAT
  which uses Watcom Compatible Math LIBs. (see math.txt).  QLINK uses the
  Borland Compatible LIBs unless you give it the /w option (so be careful
  and do not mix Borland and Watcom generated code)

  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 any of the *2exe.bat files are used 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 hold the PMWSETUP program or anything
  else you need to run after each time you compile your programs.
  See \test\spawn.set to see what I mean and try compiling spawn.asm with
  masm2exe.bat to see what I mean.

  When using the .SET files the order in which you use QSETUP, PMWLITE and
  PMWSETUP is very important because PMWLITE strips the PMODEW DOS extender
  and then adds a new one after compression is complete.  So this is the
  prefered order:
    QSETUP - this must be before PMWLITE
    QLITE or PMWLITE - this must be after QSETUP
    PMWSETUP - this must be after PMWLITE and QLITE
  Otherwise options may be wiped out after QLITE or PMWLITE is run.

  If you will not need to use QSETUP then the best thing to do is use
  the /c option with the BAT files so the EXE is already compressed
  before running the .SET file.

TTYL


