2 Parr Research Corporation
4 Purdue University Electrical Engineering
6 University of Minnesota, AHPCRC
14 A central place for information about PCCTS 1.33 is:
16 http://www.polhode.com/pccts.html
18 The maintenance release is available from:
20 http://www.polhode.com/pccts133mr.zip
22 There is a ready-to-run version for win32 for Microsoft Visual Studio
23 at the same site. It is available from:
25 http://www.polhode.com/win32.zip
27 New users should visit http://www.polhode.com/pccts.html in
28 order to get the following document:
30 "Notes For New Users of PCCTS"
32 This is a Postscript file of about 40 pages which is extremely
33 useful for someone starting out. It is a based on 1.33mr21
35 When you have a little more experience, be sure to review the
36 following documents in the distribution kit:
39 CHANGES_FROM_133_BEFORE_MR13.txt
42 -------------------------------------------------------------------------
44 -------------------------------------------------------------------------
45 0. Download http://www.polhode.com/pccts133mr.zip
47 1. Unzip the distribution kit to your preferred location.
48 If there are newline problems try using zip -a ...
50 2. cd to the main pccts directory.
61 4. Copy to /usr/local/bin or /usr/local/bin if you like. If you
62 don't wish to then add pccts/bin to your path.
64 5. To get an up-to-date list of program options execute the
65 program with no command line options. To get up-to-date
66 documentation read CHANGES_FROM_133*.txt and KNOWN_PROBLEMS.txt
69 http://www.polhode.com/pccts.html
71 6. You need not create a library. The makefile created by genmk
72 assumes that the files are not part of a library.
74 If you wish to create a library from elements of pccts/h:
76 If the first letter of the filename is lowercase (uppercase) it is
77 related to the code generated using the pccts C mode (C++ mode).
78 Some of the .c and .cpp files in the h directory are not meant to
79 be placed in a library and will not compile because they are meant
80 to be #include in pccts generated files which are grammar specific.
82 For C++ users place the following elements in the library:
87 BufFileInput.cpp (optional)
92 -------------------------------------------------------------------------
94 -------------------------------------------------------------------------
96 I've tried to keep the win32 kit to the minimum necessary to get
97 up and running. The complete kit contains additional information
98 (some historical), source code, and DevStudio projects for
99 rebuilding pccts from the source code.
101 The kit is now distributed with both MSVC 5 and MSVC6 style projects.
103 0. Download http://www.polhode.com/win32.zip.
105 You may also wish to download:
107 http://www.polhode.com/CHANGES_FROM_133.txt
108 http://www.polhode.com/CHANGES_FROM_133_BEFORE_MR13.txt
109 http://www.polhode.com/KNOWN_PROBLEMS.txt
111 1. Unzip the distribution kit to your preferred location.
115 a pccts directory tree
122 an example directory tree
123 pccts\example\calcAST\*
124 pccts\example\simple\*
126 2. Define the environment variable PCCTS to point to the main
129 3. Try building the simple project: pccts\example\simple\simple50.dsw
132 4. Try building the complex project: pccts\example\calcAST\calcAST50.dsw
135 -------------------------------------------------------------------------
136 INSTALLATION (DEC/VMS)
137 -------------------------------------------------------------------------
139 DEC/VMS support added by Piéronne Jean-François (jfp@altavista.net)
141 0. Download http://www.polhode.com/pccts133mr.zip
143 1. Unzip the distribution kit to your preferred location.
145 2. set default to the main pccts directory.
149 This will create in directory [.bin]:
156 5. To get an up-to-date list of program options execute the
157 program with no command line options. To get up-to-date
158 documentation read CHANGES_FROM_133*.txt and KNOWN_PROBLEMS.txt
159 at http://www.polhode.com/pccts.html.