]>
Commit | Line | Data |
---|---|---|
3eb9473e | 1 | ---------------------------------------------------------------------------------\r |
2 | README for pccts 1.33mr20 (Maintenance Release #20) release date 5 August 1999\r | |
3 | ---------------------------------------------------------------------------------\r | |
4 | \r | |
5 | Parr Research Corporation\r | |
6 | with\r | |
7 | Purdue University Electrical Engineering\r | |
8 | and\r | |
9 | University of Minnesota, AHPCRC\r | |
10 | \r | |
11 | Terence Parr\r | |
12 | Russell Quong\r | |
13 | Will Cohen\r | |
14 | Hank Dietz\r | |
15 | \r | |
16 | \r | |
17 | A central place for information about PCCTS 1.33 is:\r | |
18 | \r | |
19 | http://www.polhode.com/pccts.html\r | |
20 | \r | |
21 | The maintenance release is available from:\r | |
22 | \r | |
23 | http://www.polhode.com/pccts133mr.zip\r | |
24 | \r | |
25 | There is a ready-to-run version for win32 for Microsoft Visual Studio\r | |
26 | at the same site. It is available from:\r | |
27 | \r | |
28 | http://www.polhode.com/win32.zip\r | |
29 | \r | |
30 | There is a newsgroup dedicated to pccts 1.33 and related topics:\r | |
31 | \r | |
32 | comp.compilers.tools.pccts\r | |
33 | \r | |
34 | You may also want to register for the antlr-interest mailing list\r | |
35 | which is provided gratis by the following service:\r | |
36 | \r | |
37 | http://www.onesite.com\r | |
38 | \r | |
39 | New users should visit http://www.polhode.com/pccts.html in\r | |
40 | order to get the following document:\r | |
41 | \r | |
42 | "Notes For New Users of PCCTS"\r | |
43 | \r | |
44 | This is a Postscript file of about 40 pages which is extremely \r | |
45 | useful for someone starting out. It is a based on 1.33mr7 so is a\r | |
46 | little bit out-of-date. The section on semantic predicates is\r | |
47 | very out of date, but I have not had time to revise it.\r | |
48 | \r | |
49 | When you have a little more experience, be sure to review the\r | |
50 | following documents in the distribution kit:\r | |
51 | \r | |
52 | CHANGES_FROM_133.txt\r | |
53 | CHANGES_FROM_133_BEFORE_MR13.txt\r | |
54 | KNOWN_PROBLEMS.txt\r | |
55 | \r | |
56 | -------------------------------------------------------------------------\r | |
57 | INSTALLATION (Unix)\r | |
58 | -------------------------------------------------------------------------\r | |
59 | 0. Download http://www.polhode.com/pccts133mr.zip\r | |
60 | \r | |
61 | 1. Unzip the distribution kit to your preferred location.\r | |
62 | \r | |
63 | 2. cd to the main pccts directory.\r | |
64 | \r | |
65 | 3. make\r | |
66 | \r | |
67 | This will create:\r | |
68 | \r | |
69 | antlr.exe\r | |
70 | dlg.exe\r | |
71 | sorcerer.exe\r | |
72 | genmk.exe\r | |
73 | \r | |
74 | 4. Add pccts/bin to your path.\r | |
75 | \r | |
76 | 5. To get an up-to-date list of program options execute the\r | |
77 | program with no command line options. To get up-to-date\r | |
78 | documentation read CHANGES_FROM_133*.txt and KNOWN_PROBLEMS.txt\r | |
79 | at:\r | |
80 | \r | |
81 | http://www.polhode.com/pccts.html.\r | |
82 | \r | |
83 | 6. You need not create a library. The makefile created by genmk\r | |
84 | assumes that the files are not part of a library. \r | |
85 | \r | |
86 | If you wish to create a library from elements of pccts/h:\r | |
87 | \r | |
88 | If the first letter of the filename is lowercase (uppercase) it is\r | |
89 | related to the code generated using the pccts C mode (C++ mode).\r | |
90 | Some of the .c and .cpp files in the h directory are not meant to\r | |
91 | be placed in a library and will not compile because they are meant\r | |
92 | to be #include in pccts generated files which are grammar specific.\r | |
93 | \r | |
94 | For C++ users place the following elements in the library:\r | |
95 | \r | |
96 | AParser.cpp\r | |
97 | ASTBase.cpp\r | |
98 | ATokenBuffer.cpp\r | |
99 | BufFileInput.cpp (optional)\r | |
100 | DLexerBase.cpp\r | |
101 | PCCTSAST.cpp\r | |
102 | SList.cpp\r | |
103 | \r | |
104 | -------------------------------------------------------------------------\r | |
105 | INSTALLATION (Win32)\r | |
106 | -------------------------------------------------------------------------\r | |
107 | \r | |
108 | I've tried to keep the win32 kit to the minimum necessary to get \r | |
109 | up and running. The complete kit contains additional information\r | |
110 | (some historical), source code, and DevStudio projects for \r | |
111 | rebuilding pccts from the source code.\r | |
112 | \r | |
113 | The kit is now distributed with both MSVC 5 and MSVC6 style projects.\r | |
114 | \r | |
115 | 0. Download http://www.polhode.com/win32.zip.\r | |
116 | \r | |
117 | You may also wish to download:\r | |
118 | \r | |
119 | http://www.polhode.com/CHANGES_FROM_133.txt\r | |
120 | http://www.polhode.com/CHANGES_FROM_133_BEFORE_MR13.txt\r | |
121 | http://www.polhode.com/KNOWN_PROBLEMS.txt\r | |
122 | \r | |
123 | 1. Unzip the distribution kit to your preferred location.\r | |
124 | \r | |
125 | This will create:\r | |
126 | \r | |
127 | a pccts directory tree\r | |
128 | pccts/bin/*.exe\r | |
129 | pccts/lib/*.lib\r | |
130 | pccts/h/*\r | |
131 | sorcerer/lib/*\r | |
132 | sorcerer/h/*\r | |
133 | \r | |
134 | an example directory tree\r | |
135 | example\calcAST\*\r | |
136 | example\simple\*\r | |
137 | \r | |
138 | 2. Define the environment variable PCCTS to point to the main\r | |
139 | pccts directory.\r | |
140 | \r | |
141 | 3. Try building the simple project: example\simple\simple50.dsw\r | |
142 | or simple60.dsw.\r | |
143 | \r | |
144 | 4. Try building the complex project: example\calcAST\calcAST50.dsw\r | |
145 | or calcAST60.dsw.\r | |
146 | \r | |
147 | -------------------------------------------------------------------------\r | |
148 | INSTALLATION (DEC/VMS)\r | |
149 | -------------------------------------------------------------------------\r | |
150 | \r | |
151 |