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