|
1 | 1 | BUILDING PYTHON 1.2 FOR THE MACINTOSH |
2 | 2 | ************************************* |
3 | 3 |
|
4 | | -Python can be built on the Mac using either THINK C 6.0 (or 7.0), MPW |
5 | | -3.2, or CodeWarrior 5.0. In the past it has also been compiled with |
6 | | -earlier versions of Think and MPW, but no guarantees are made that the |
7 | | -source is still compatible with those versions. Think C 5.0 appears |
8 | | -to be OK. Likewise, new compiler versions may effectively change the |
| 4 | +Python can be built on the Mac using either THINK C 6.0 (or 7.0), or |
| 5 | +CodeWarrior 5.0 (for 68K and PPC). In the past it has also been compiled |
| 6 | +with earlier versions of Think, but no guarantees are made that the |
| 7 | +source is still compatible with those versions. (Think C 5.0 appears |
| 8 | +to be OK.) Likewise, new compiler versions may effectively change the |
9 | 9 | language accepted (or the library provided!) and thus cause problems. |
10 | 10 |
|
| 11 | +MPW is a special case -- it used to be possible to build Python as |
| 12 | +an MPW tool using MPW 3.2, and this may still work, but I haven't |
| 13 | +tried this lately. What I have tried, however, is building Python |
| 14 | +as a shared library for CFM-68K, using the Symantec C compiler for MPW. |
| 15 | +See subdirectory MPW and the README file there for more info. |
| 16 | + |
11 | 17 |
|
12 | 18 | 1. Using Think C 6.0 (or 7.0) |
13 | 19 | ============================= |
@@ -151,36 +157,7 @@ to it. It is lying. What you should do instead is "Check Link..." |
151 | 157 | and _then_ hit Run. Why? Ask Symantec. |
152 | 158 |
|
153 | 159 |
|
154 | | -2. Using MPW 3.2 |
155 | | -================ |
156 | | - |
157 | | -The subdirectory MPW contains a README.MPW file, a buildall script and |
158 | | -several Makefiles, kindly contributed by Richard Walker of Island |
159 | | -Software. Move these files to the corresponding locations relative to |
160 | | -the Python root directory (where Mac-Makefile should become Makefile |
161 | | -in the Mac subdirectory, etc.), and run the buildall script. The |
162 | | -README.MPW file contains more instructions and caveats (I've added |
163 | | -some remarks of my own at the end). |
164 | | - |
165 | | -Some notes: |
166 | | - |
167 | | -- The MPW and THINK C ports share all source files, including config.c |
168 | | - and config.h -- all differentiation is done based on #ifdef THINK_C |
169 | | - or #ifdef MPW (#ifdef macintosh is used for code that should be seen |
170 | | - by all Mac compilers). |
171 | | - |
172 | | -- The dynload subdirectory contains an attempt to create dynamically |
173 | | - loadable modules from CODE segments. This was not very successful |
174 | | - due to the restrictions on CODE segments (no global variables, no |
175 | | - calls to external functions). Maybe Apple's new shared library |
176 | | - manager will be a better starting point. |
177 | | - |
178 | | -- I haven't tried building STDWIN with MPW recently. There is MPW |
179 | | - specific code all over the STDWIN source but it is for a much older |
180 | | - version of the compiler and library. |
181 | | - |
182 | | - |
183 | | -3. Using MicroWerks CodeWarrior 5.0 |
| 160 | +2. Using MicroWerks CodeWarrior 5.0 |
184 | 161 | =================================== |
185 | 162 |
|
186 | 163 | Essentially, follow the instructions for Think C. |
|
0 commit comments