@@ -5,10 +5,8 @@ Python can be built on the Mac using either THINK C 6.0 or MPW 3.2.
55In the past it has been compiled with earlier versions of these
66compilers, but no guarantees are made that the source is still
77compatible with those versions. Likewise, new compiler versions may
8- effectively change the language accepted (or the library!) and thus
9- cause problems.
10-
11- [[MPW version and procedure must still be checked]]
8+ effectively change the language accepted (or the library provided!)
9+ and thus cause problems.
1210
1311
14121. Using Think C 6.0
@@ -102,21 +100,14 @@ arbitrarily because of the 32000 bytes restriction.
102100 macmodule.c in the Mac subdirectory, so it should already have
103101 been added in a previous step.) Note that for most modules,
104102 the source file is called <name>module.c, but for a few long
105- module names it is just <module>.c.
103+ module names it is just <module>.c. Don't add stdwinmodule.c
104+ yet,
106105
107106The following THINK C libraries must be added: from Standard
108107Libraries, ANSI and unix; from Mac Libraries, MacTraps. I put each
109108library in a separate segment. Also see my earlier remark on 4-byte
110109ints.
111110
112- 1.3 Living without STDWIN
113- -------------------------
114-
115- Although STDWIN is really neat on the Mac, it's easier to begin
116- building Python without it, so you can concentrate on the Python
117- build. To this end, you have to comment out the lines defining the
118- symbol USE_STDWIN in macmain.c and config.c.
119-
1201111.4 Adding STDWIN
121112-----------------
122113
@@ -127,9 +118,10 @@ the same general source setup (in a sister directory of the toplevel
127118Python directory). Put all sources in the same segment. To
128119stdwin.pi, also add Tools/strdup.c and Gen/wtextbreak.c.
129120
130- The two projects can now be added as libraries to the Python project,
131- and the two lines commented out to live without STDWIN should be
132- reinstated.
121+ The two projects can now be added as libraries to the Python project.
122+ You must also add stdwinmodule.c and add "#define USE_STDWIN" to the
123+ Prefix in the compiler options dialog (this only affects macmain.c and
124+ config.c).
133125
134126Note that stdwinmodule.c contains an #include statement that
135127references "stdwin.h" by relative path name -- if the stdwin toplevel
@@ -147,13 +139,21 @@ copies resources into the application file from a file
147139<projectname>.rsrc.
148140
149141
150- 2. Using MPW
151- ============
152-
153- See the subdirectory MPW. I haven't tried this recently. You're
154- supposed to merge the directory tree found here with the UNIX source
155- tree. I think this is intended for use with MPW 3.2. The dynload
156- stuff in not recommended.
142+ 2. Using MPW 3.2
143+ ================
144+
145+ The subdirectory MPW contains a README.MPW file, a buildall script and
146+ several Makefiles (in respective subdirectories), kindly contributed
147+ by Richard Walker of Island Software. Move these files to the
148+ corresponding locations relative to the Python root directory, and run
149+ the buildall script. The README.MPW file contains more instructions
150+ and caveats (I've added some remarks of my own at the end). I haven't
151+ tried building STDWIN with MPW recently (there is MPW specific code
152+ all over the STDWIN source but it is for a much older version of the
153+ compiler and library). The MPW and THINK C ports share all source
154+ files, including config.c and config.h -- all differentiation is done
155+ based on #ifdef THINK_C or #ifdef MPW (#ifdef macintosh is used for
156+ code that should be seen by all Mac compilers).
157157
158158
159159--Guido van Rossum, CWI, Amsterdam <
[email protected] >
0 commit comments