Building the Livingstone2 Engine

Back to Main Page

 

 

 
 Windows:
 --------
 Make sure you have checked out the following modules from CVS
 in the same directory:
 
   L2           - Creates the directory mba
   xml-windows  - Creates the directory support/xerces
   l2-regress   - Creates the directory l2-regress
 
 Open mba/mba.dsw in Visual C++ 6.0.  

 First, select Project->Set Active Project: livdll, and then Build->Rebuild All.

 Then select any of the following
 projects as the default and build it:
 
   "l2test files"  - Reads a model in any format and provides a
                     command-line interface to test the L2 engine.
   "xml2l2 files"  - Takes a model in XMPL format and produces a file
                     in l2 format, with debugging info.
 
 Once built, the executables are stored in the mba/cpp/bin directory.
 
 
 Unix (Solaris, Linux, Irix):
 ----------------------------
 Check out the modules you'll need:
        cvs co mba/cpp support/xerces-unix-src
 Then, read
        mba/cpp/BUILD
 which will have up-to-date instructions.
 
 
 VxWorks:
 --------
 Make sure you have checked out the following modules from CVS
 in the same directory:
 
   L2           - creates the directory mba
   xerces       - creates the directory xerces
 
 Note for Tornado Windows users: When checking Tornado workspace and
 project files out of CVS, the files will have to be converted to use
 Unix end of line characters before Tornado can open them.
 
 Open mba/mba.wsp in Tornado.  Build the following projects as
 required:
 
   "readers Files"    - must be built first and is required for the
                        "l2run Files" and "l2test Files" projects.
   "XercesLib Files"  - required for reading xmpl files.
   "l2test Files"     - Reads a model in any format and provides a
                        command-line interface to test the L2 engine.
 
 If XMPL files is going to be read, the "XercesLib Files" projects must
 be downloaded to the target first before the "l2test Files" project. If
 other formats are going to be read, only the "l2test Files" project
 file has to be download, but there will be unresolved references to
 functions that are in the "XercesLib Files" project. These can be ignore
 as long as an XMPL file is not going to be read.
 
 To start the L2 engine, the following function must be called:
 l2test(char*, char*, char*). The first char* is a command line
 string. The second char* is an optional input redirection from
 file string and the third char* is an optional output redirection
 to file string. For example calling through the WindShell:
 
   -> l2test("/tgtsvr/x37V1p6.l2 --history=2", "/tgtsvr/nominal.scr")
 
      Notice that the third parameter is missing. The WindShell
      will automatically pass a null in the third parameter.
 
 The "l2test" function calls the L2 engine that reads the x37V1p6.l2
 file from the target server directory and then set the history to 2.
 Keyboard input is taken from the nominal script file, located in the
 target server directory. Output is redirected to standard out.