* RCS $Id: readme.txt,v 1.2 1995/09/07 15:07:16 ae59 Exp $ *
 =====================================================================
    Installation Notes for the PASCAL-XSC Runtime System
 
   Following instructions may help you to install a new rts for PXSC.
 
 =====================================================================
 I. Generating a previously installed runtime library
 ----------------------------------------------------
  There are several systems where the pxsc runtime has already been
  installed. You can use the provided Makefile to generate a runtime
  library for these computer systems. Type in <make> for a list
  of the supported systems. If you can't find your specific target,
  try a target which might be similar to yours. For example
  target <ansi-c> will work on most ansi-c compatible C compiler.
 
  Makefile will try to configure your runtime sources properly
  with the unix sed tool. OS2 can also be configured if you have
  gnu utilities installed.

  NOTE: You need a make utility and a sed utility!
        
 =====================================================================
 II. Generating a  runtime library on a new target system
 --------------------------------------------------------
 Some explanation of the provided runtime sources follows,
 which might be helpful for successful installation of
 the pxsc runtime system.

 1. In file         o_srcs.txt
 
    the file names of the required files of the PASCAL-XSC
    runtime system are listed to check for completeness.
 
 2. In file 'o_user.c' the variable
 
                       o_sdir, o_udir
 
    must hold a quoted string which refers to the default system 
    directory used by the PASCAL-XSC compiler, the default pxsc user
    directory, resp.. This name should coincide with the setting used by 
    the PASCAL-XSC compiler.
    e.g: o_sdir ="/usr/pxsc/sys/"; on multi user machines
	    o_udir ="/pxsc/";
	    o_sdir = e:\\pxsc\\sys\\"; on single user machines
	    o_udir ="";
 
 3. In file 'o_slct.h' the
 
                  installation macro
 
    must be selected by giving it a value of 1. All other
    installation macros must have value 0. Check version string !
 
 
 4. In file 'o_slct.h' the hardware macro
 
                        IEEE_HARDWARE
 
    may be selected only if the required (assembler) routines are 
    available. Up to now only IBM_RT_C/SUN/HP is supported by hardware.
 
 5. Copy the files         info.txt
                           o_msg1.h
 
    into the directory specified by o_sdir.
 
 6. In file 'p88rts.h' the configuration section have to be set
    this includes the setting of the (local) compiler switches
	 USING_LINT_ARGS : 0 - K&R prototyping, IBMva, no LINT_ARGS
				    1 - newstyle protoyping, LINT_ARGS no IBMva

      USING_AREALSTRU : 0 - a_real is double
				    1 - a_real is a structure (ATARI,VAX-systems, Cray)

      USING_64_BITSYS : 0 - non 64 bit word length system (default)
				    1 - 64 bit word length 
 
    according to the requirements of the C compiler in use.
    USING_.. switches are allowed in p88rts.h only. No more 
    changes have to be made for reinstalling a system.
 
 7. Check ALL the settings of the macros in
 
    o_slct.h   o_defs.h  o_spec.h   o_syst.h
 
    NODSTD has to be defined if no IEEE standard functions are 
           available on destination machine (o_spec.h).
    INTEL  has to be defined =1 if INTEL byte structure and hardware 
           support is available (o_syst.h).
 
    if a new installation macro is introduced and report any 
    difficulties concerning the meaning of the macros BEFORE the 
    runtime system is compiled in order to avoid time consuming 
    recompilations.
 
 
 8. Use the runtime option:   -info
 
    as command line argument in order to get informations
    about active runtime options of your installation.
 
 10. To create a for UNIX library rts.a, please type:
 
     UNIX:   start r_make.bat <arguments> or
             cc -c -O *.c # compiling sources
             cat o_tsrt.txt | xargs -n1 ar cq rts.a 

     or use make utility with the supplied Makefile.
     
 
 
 11. In case of problems, please contact:
 
               H.Berlejung  Ext. (0721) 377936
               e-mail: ae59@rz.uni-karlsruhe.de
 

 =====================================================================
 III. Version Description Document
 ---------------------------------
 There is a changes.txt file which contains the information about
 changes of each source file. 

 There is a version description document, which contains the list
 of release identifications of each source being associated to
 the current release.

 The current release is named and identified in the top of changes.txt
 The name of the release is the official release date of the library
 The release id is the actual working identification. This means that
 the release name summarizes several realease identifications.

 =====================================================================
 IV. Guess system properties     
 ---------------------------
 All runtime releases after 1992-10-31 comes with a C program
 that determines features of the current computer platform.
 The file is call sysguess.txt which should be renamed to sysguess.c.
 Then uses cc -o sysguess.exe sysguess.c to generate an executable.
 Alternatively type in make guess.

 =====================================================================
  -eof-
