install.ins

反汇编源码

------------------------------------------------------------------------
This is the 2.42 release of PRECCX  (INSTALL.INS)            August 1994
Peter T. Breuer   <[e-mail],[e-mail],[e-mail]>
All rights reserved.
------------------------------------------------------------------------ 

INSTALLATION INSTRUCTIONS FOR DOS AND UNIX.

The DOS install.exe routine should have put the components  of the dist-
ribution in place,  or at least where you told it to put them!  The UNIX
makefile likewise can be invoked with  `make install'  after the initial
`make'  and will put the relevant  files in the places  specified in the
makefile (read and check)! In case you want to change things afterwards,
here are the instructions for doing things manually:

a) Put the following files where your C compiler will find them:
 
              - HEADERS  (in PRECCXI.ZIP or PRECCX\INCLUDE)
cc.h		/* precc header file (no inherited attributes)  */
ccx.h		/* precc header file (for inherited attributes) */
      
	      - LIBRARY  (in PRECCXL.ZIP or PRECCX\LIB)
libcc1.a   (UNIX)
libcc2.a   (UNIX)
libcc4.a   (UNIX)
preccx1C.lib (DOS)
preccx2C.lib (DOS)
preccx4C.lib (DOS)
preccx1L.lib (DOS)
preccx2L.lib (DOS)
preccx4L.lib (DOS)

I can't help you with the  placing  because it will be  specific to your
installation and your compiler. But I have the headers in \home\include,
and the libraries in \home\c\lib (under DOS). Under UNIX, they are in my
$HOME/include and $HOME/c/lib directories.

b) link or copy one of the libraries to 

libcc.a   (UNIX)
preccx.lib (DOS)

You should choose libcc1.a/preccx1C.lib  if you are going to use 1-byte
TOKENs (this is normal) and the Compact memory model for C, and another
accordingly if you have a larger size or the Large model in mind.

c) Make pointers to the binary:

              - EXECUTABLES (in PRECCXX.ZIP or PRECCX\BIN)

preccx[.exe]    /* the precc executable                         */

Put this somewhere where your operating  system will find it.  That has
to be in a directory named in your PATH variable.  Or make a PRECCX.BAT
file (DOS) or executable shell script (UNIX) containing the single line

    preccx %1 %2 %3 %4 %5 %6 %7 %8 %9            (DOS)
    preccx $*                                    (UNIX)

replacing  `preccx'  with the exact location of the binary  executable.
The BAT/shell file should then be placed somewhere in the PATH instead.
I have a BAT file in \bin\bat and a shell script in $HOME/bin.

d) Read the literature:
              - MANUALS (in PRECCXD.ZIP or PRECCX\MAN)

   preccx.1   (UNIX: use nroff -man preccx.1 | more)
   preccx.m   (DOS: use more <preccx.m)
   README.EXE (DOS only)

Also provided is a long technical paper in ascii and .DVI format.
This should be viewable using dviscr, dvivga or other publicly
available dvi previewers.

   preccx.t    (DOS: use more <preccx.t,    UNIX: more preccx.t)
   preccx.dvi  (DOS: use dviscr preccx.dvi, UNIX: dvitool preccx or equiv.)

YOU ARE READY TO GO. NOW READ THE FILE RUN.INS IN THIS DIRECTORY.