Excerpts from message dated 05-19-95, David Galbraith to Paul Edwards.
The original subject was: "Borland 1.5 on CD," and the post was an
answer to Paul's query as to how to run the compiler from a CD.  David
describes a very good way to set up running more than one compiler from
the same system, even if not from a CDROM.  David's procedure can be
simplified if running under Warp:

DG>1)  Set the LIBPATH in config.sys assuming that the 
  >    required CD is in     the drive.

DG>    LIBPATH = .;E:\OS2\DLL;...;H:\WATCOM\BINP\DLL;
  >    H:\WATCOM\SOM\LIB;H:\IBMCPP\DLL;

    Usually no longer necessary if you are using Warp.  See below.

DG>2)  Having a command file to set the appropriate 
  >    environment variables for each compiler.  My 
  >    csetenv.cmd file follows.
  >   
  >        {at}ECHO OFF
  >        SET PATH = %PATH%H:\IBMCPP\BIN; 
  >        SET DPATH = %DPATH%H:\IBMCPP\LOCALE;H:\IBMCPP\HELP;
  >                    H:\IBMCPP\SYS;
....remainder of sample csetenv.cmd deleted...

DG>3)  I have an icon set up for each compiler which gives me 
  >    a command line with the relevant parameters set.  I do 
  >    this by creating a new program object and placing a * in
  >    the path and file name and a pointer to the command file
  >    preceded by a /K in the parameters section.  In my case
  >    this is /K F:\BIN\OS2\CSETENV.CMD. 

David--

    If you are using Warp, your config.sys LIBPATH usually doesn't need
to show the paths to the directories that contain only compiler-specific
DLLs.  There is a new (poorly-documented) pair of session-specific
commands: "BeginLibPath" and "EndLibPath" that can be
enabled with SET
commands in the command file calling the session.  The corresponding API
calls are DosSetExtLIBPATH and DosQueryExtLIBPATH.

    You can find a very few words of wisdom describing these "SET"
commands in the printed (US) version of Warp "Control Programming
Programming Guide" (p/n G25H-7101-00) through the index entry: "LIBPATH,
Extended."  You can find the descriptions of the API calls in the
corresponding "Programming Reference" (p/n G25H-7102-00) only if you
already know their names!  The API information is also in the on-line
manual dealing with the Control Program that comes with the WarpTlkt
(available only through DevCon, AFAIK).  (I couldn't find anything about
the SET versions in the on-line manual, but I rarely can find anything
in an on-line doc, even when I know it is there )

    These two commands cause a config.sys LIBPATH search to be preceded,
or followed, by searches of the paths defined as specific to the
session.  I use: SET BEGINLIBPATH=H:\IBMCPP\DLL;H:\TOOLKIT\DLL; in my
version of csetenv.cmd, and similar statements in the equivalent command
files setting the session environments for the other compilers I use,
even though I do not compile from a CD.  The only compiler-specific DLL
paths in my config.sys file are for use with programs compiled to be
executed with the compiler's RTL DLL (e.g. by PL/I), which may be used
outside of the compiler session.

    I have also used this "command file" technique to check out the
effects of using WarpTlkt as compared to Toolkt21, with CSet++.  I set
up separate desktop icons for two sessions of CSet++ that differed only
by which toolkit was used for the compilation.

    This is a very convenient technique to shorten the config.sys
LIBPATH string.  Wonderful what you can do with Warp!

          --Murray
___
 * MR/2 2.23 #120 * One printed manual is worth a thousand INF files
                                                      
---