1- BUILDING PYTHON 1.1 FOR THE MACINTOSH
1+ BUILDING PYTHON 1.2 FOR THE MACINTOSH
22*************************************
33
4- Python can be built on the Mac using either THINK C 6.0 (or 7.0) or
5- MPW 3.2. In the past it has been compiled with earlier versions of
6- these compilers , but no guarantees are made that the source is still
7- compatible with those versions. Likewise, new compiler versions may
8- effectively change the language accepted (or the library provided!)
9- and thus cause problems.
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
9+ language accepted (or the library provided!) and thus cause problems.
1010
1111
12- 1. Using Think C 6.0
13- ====================
12+ 1. Using Think C 6.0 (or 7.0)
13+ =============================
1414
15151.1 The directory structure
1616---------------------------
@@ -64,7 +64,9 @@ prevent parsing larger modules.
6464 slower, but Python programs can use strings and lists with
6565 more than 32000 items (with 2-byte ints these can cause
6666 crashes). The range of Python integers is not affected (these
67- are always represented as longs).
67+ are always represented as longs). In fact, nowadays I always
68+ use 4-byte integers, since it is actually rather annoying that
69+ strings >= 64K cause crashes.
6870
69711.2.3 Files to add
7072
@@ -77,19 +79,18 @@ compile.c in a separate segment. You could also group them by
7779subdirectory or function, but you may still have to split segments
7880arbitrarily because of the 32000 bytes restriction.
7981
80- - From Mac: all .c files except fopenRF.c [[which shouldn't even
81- be there]].
82+ - From Mac: all .c files.
8283
83- - From Parser: acceler.c, grammar1.c, intrcheck.c,
84+ - From Parser: acceler.c, grammar1.c,
8485 myreadline.c, node.c, parser.c, parsetok.c, tokenizer.c.
8586
8687 - From Python: bltinmodule.c, ceval.c, cgensupport.c,
87- compile.c, errors.c, getopt.c, graminit.c, import.c,
88- marshal .c, modsupport .c, mystrtoul .c, pythonmain .c,
89- pythonrun .c, sigcheck .c, structmember .c, sysmodule .c,
90- traceback.c (i.e. all .c files except dup2.c, fmod .c,
91- frozenmain .c, getcwd .c, getmtime .c, memmove .c, sigcheck .c,
92- strerror.c, strtod.c, thread.c)
88+ compile.c, errors.c, getargs.c getopt.c, graminit.c, import.c,
89+ importdl .c, marshal .c, modsupport .c, mystrtoul .c,
90+ pythonmain .c, pythonrun .c, sigcheck .c, structmember .c,
91+ sysmodule.c, traceback.c (i.e. all .c files except dup2.c,
92+ fmod .c, frozenmain .c, getcwd .c, getmtime .c, memmove .c,
93+ sigcheck.c, strerror.c, strtod.c, thread.c)
9394
9495 - From Objects: all .c files except xxobject.c.
9596
@@ -138,6 +139,17 @@ distributed Python application with ResEdit. THINK C automatically
138139copies resources into the application file from a file
139140<projectname>.rsrc.
140141
142+ 1.6 Think C 5.0
143+ ---------------
144+
145+ Tim Gilbert adds one note that will be helpful to future Think C 5.0
146+ users: When you have a really big project like python, and you want to
147+ compile and run it, if you just hit Command-R, often Think C will
148+ compile the remaining files, think for a moment, and then give you a
149+ warning "internal error(ZREF)--please remove objects." Don't listen
150+ to it. It is lying. What you should do instead is "Check Link..."
151+ and _then_ hit Run. Why? Ask Symantec.
152+
141153
1421542. Using MPW 3.2
143155================
@@ -168,5 +180,13 @@ Some notes:
168180 version of the compiler and library.
169181
170182
183+ 3. Using MicroWerks CodeWarrior 5.0
184+ ===================================
185+
186+ Essentially, follow the instructions for Think C.
187+
188+ XXX Should at least list the project options.
189+
190+
171191--Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>
172192<URL:http://www.cwi.nl/cwi/people/Guido.van.Rossum.html>
0 commit comments