@@ -58,7 +58,14 @@ <H2>What you need.</H2>
5858HREF ="ftp://sunsite.cnlab-switch.ch/software/platform/macos/src ">
5959ftp://sunsite.cnlab-switch.ch/software/platform/macos/src</ A > .
6060At the moment Python is built with a slightly modified version of GUSI,
61- these modifications are available in folder < code > Python:Mac:GUSI-mods</ code > .
61+ these modifications are available in folder < code > Python:Mac:GUSI-mods</ code > . < br >
62+
63+ The modified GUSI is also in the MacPython cvs source repository, in the
64+ directory < code > lib-src/CWGUSI</ code > . However, some files contain slashes in
65+ their names, something CVS seriously frowns upon, and each slash has been
66+ replaced by < code > "_s_"</ code > . There is a script
67+ < code > Mac:scripts:fixgusidir.py</ code > which you should run after checking CWGUSI
68+ out
6269
6370</ UL >
6471
@@ -91,20 +98,24 @@ <H2>What you need.</H2>
9198< LI > Gdbm library for the Mac. Available from Jack's Mac software page at
9299< A HREF ="http://www.cwi.nl/~jack/macsoftware.html ">
93100http://www.cwi.nl/~jack/macsoftware.html</ A > and < A HREF ="ftp://ftp.cwi.nl/pub/jack/mac ">
94- ftp://ftp.cwi.nl/pub/jack/mac</ A > .
101+ ftp://ftp.cwi.nl/pub/jack/mac</ A > . Also in the MacPython cvs repository at
102+ < code > lib-src/gdbm</ code > .
95103
96104< LI > JPEG library by the Independent JPEG Group. A version including
97105Mac projects can be found at Jack's page mentioned above.
98106The most recent JPEG library can always be obtained from < A
99- HREF ="ftp://ftp.uu.net/graphics/jpeg/ "> ftp://ftp.uu.net/graphics/jpeg/</ A > .
107+ HREF ="ftp://ftp.uu.net/graphics/jpeg/ "> ftp://ftp.uu.net/graphics/jpeg/</ A > . Again,
108+ also in the MacPython cvs repository at < code > lib-src/jpeg</ code > .
100109
101110< LI > The netpbm/pbmplus, libtiff, zlib and png libraries. The netpbm distribution
102111(which includes libtiff) is generally available on Internet ftp
103112servers. For Python pbmplus, an older incarnation of netpbm, is
104113functionally identical to netpbm, since Python only uses the library
105114and not the complete applications. A distribution with correct
106115projects and library source only is available from, you guessed it, Jack's Mac software
107- page mentioned above.
116+ page mentioned above. And, guessed it again, in the MacPython cvs repository
117+ at < code > lib-src/netpbm</ code > , etc. The only gotcha is that libtiff lives in
118+ < code > lib-src/netpbm/libtiff</ code > , for historical reasons.
108119
109120</ UL >
110121
@@ -199,9 +210,10 @@ <H2>The organization of the Python source tree</H2>
199210
200211< DT > Extensions
201212< DD > Extensions to the interpreter that are not Mac-specific. Contains
202- only the < code > img</ code > extension in this distribution. Extensions
203- are not always built here, as they are on Unix, but sometimes incorporated in
204- the core interpreter or built as plugin modules.
213+ the < code > img</ code > , < code > Imaging</ code > and < code > Numeric</ code > extensions
214+ in this distribution. Nowadays, the extensions are all built in their own
215+ folders (unlike in older distributions, where img was incorporated in the main
216+ build procedure).
205217
206218< DT > Grammar
207219< DD > The Python grammar. Included for reference only, you cannot build
@@ -240,7 +252,7 @@ <H2>The organization of the Python source tree</H2>
240252< DD > This is where the project files live and where you build the
241253libraries, shared libraries, executables and plugin modules. All the
242254resulting binaries, except for intermedeate results, are deposited in
243- the toplevel folder or the PlugIns folder (for plugin modules).
255+ the toplevel folder or the Mac: PlugIns folder (for plugin modules).
244256
245257< DT > Compat
246258< DD > Unix-compatability routines. Some of these are not used anymore,
@@ -364,7 +376,8 @@ <H2>Building the PPC and CFM68K interpreter</H2>
364376applet. < p >
365377
366378< DT > Plugin projects
367- < DD > Usually, each plugin module has a separate project.
379+ < DD > Each plugin module has a separate project. The < code > Plugins.prj</ code >
380+ project tries to build them all, but is known to be flakey under CW Pro 4.
368381</ DL >
369382
370383After creating the alias to < code > PythonCore</ code > you remove any old
@@ -374,11 +387,8 @@ <H2>Building the PPC and CFM68K interpreter</H2>
374387
375388Next, you have to build the extension modules.
376389The < code > PlugIns.ppc</ code > project has all the
377- other projects as subprojects and builds everything. After all
378- the dynamically loaded modules are built you have to create a number
379- of aliases: some modules live together in a single dynamic
380- library. Run the < code > ConfigurePython.py</ code > script from
381- < code > Mac:scripts</ code > to create the aliases. < p >
390+ other projects as subprojects and builds everything (but see the gotcha above).
391+ < p >
382392
383393Finally, you must build the standard applets:
384394< code > EditPythonPrefs</ code > , < code > BuildApplet</ code > , etc. This is
0 commit comments