From a598bc412c6895244961fb0b8f33dbea6e26cf65 Mon Sep 17 00:00:00 2001 From: Jack Jansen Date: Wed, 10 Feb 1999 23:08:24 +0000 Subject: [PATCH] Updated for the new one-slb-per-extension scheme. Added a few references to cvs locations for external libraries. img now builds in its own Extensions folder. --- Mac/Demo/building.html | 38 ++++++++++++++++++++++++-------------- 1 file changed, 24 insertions(+), 14 deletions(-) diff --git a/Mac/Demo/building.html b/Mac/Demo/building.html index 03c48ce753a..f78b2b729d5 100644 --- a/Mac/Demo/building.html +++ b/Mac/Demo/building.html @@ -58,7 +58,14 @@ obtainable from ftp://sunsite.cnlab-switch.ch/software/platform/macos/src. At the moment Python is built with a slightly modified version of GUSI, -these modifications are available in folder Python:Mac:GUSI-mods. +these modifications are available in folder Python:Mac:GUSI-mods.
+ +The modified GUSI is also in the MacPython cvs source repository, in the +directory lib-src/CWGUSI. However, some files contain slashes in +their names, something CVS seriously frowns upon, and each slash has been +replaced by "_s_". There is a script +Mac:scripts:fixgusidir.py which you should run after checking CWGUSI +out @@ -91,12 +98,14 @@ and various other places.
  • Gdbm library for the Mac. Available from Jack's Mac software page at http://www.cwi.nl/~jack/macsoftware.html and -ftp://ftp.cwi.nl/pub/jack/mac. +ftp://ftp.cwi.nl/pub/jack/mac. Also in the MacPython cvs repository at +lib-src/gdbm.
  • JPEG library by the Independent JPEG Group. A version including Mac projects can be found at Jack's page mentioned above. The most recent JPEG library can always be obtained from ftp://ftp.uu.net/graphics/jpeg/. +HREF="ftp://ftp.uu.net/graphics/jpeg/">ftp://ftp.uu.net/graphics/jpeg/. Again, +also in the MacPython cvs repository at lib-src/jpeg.
  • The netpbm/pbmplus, libtiff, zlib and png libraries. The netpbm distribution (which includes libtiff) is generally available on Internet ftp @@ -104,7 +113,9 @@ servers. For Python pbmplus, an older incarnation of netpbm, is functionally identical to netpbm, since Python only uses the library and not the complete applications. A distribution with correct projects and library source only is available from, you guessed it, Jack's Mac software -page mentioned above. +page mentioned above. And, guessed it again, in the MacPython cvs repository +at lib-src/netpbm, etc. The only gotcha is that libtiff lives in +lib-src/netpbm/libtiff, for historical reasons. @@ -199,9 +210,10 @@ work, the file README-Mac has some details.
    Extensions
    Extensions to the interpreter that are not Mac-specific. Contains -only the img extension in this distribution. Extensions -are not always built here, as they are on Unix, but sometimes incorporated in -the core interpreter or built as plugin modules. +the img, Imaging and Numeric extensions +in this distribution. Nowadays, the extensions are all built in their own +folders (unlike in older distributions, where img was incorporated in the main +build procedure).
    Grammar
    The Python grammar. Included for reference only, you cannot build @@ -240,7 +252,7 @@ All the mac-specific stuff lives in the Mac folder:
    This is where the project files live and where you build the libraries, shared libraries, executables and plugin modules. All the resulting binaries, except for intermedeate results, are deposited in -the toplevel folder or the PlugIns folder (for plugin modules). +the toplevel folder or the Mac:PlugIns folder (for plugin modules).
    Compat
    Unix-compatability routines. Some of these are not used anymore, @@ -364,7 +376,8 @@ file, and add a 'PYC ' with the module to generate an applet.

    Plugin projects -
    Usually, each plugin module has a separate project. +
    Each plugin module has a separate project. The Plugins.prj +project tries to build them all, but is known to be flakey under CW Pro 4. After creating the alias to PythonCore you remove any old @@ -374,11 +387,8 @@ to create the correct preferences file.

    Next, you have to build the extension modules. The PlugIns.ppc project has all the -other projects as subprojects and builds everything. After all -the dynamically loaded modules are built you have to create a number -of aliases: some modules live together in a single dynamic -library. Run the ConfigurePython.py script from -Mac:scripts to create the aliases.

    +other projects as subprojects and builds everything (but see the gotcha above). +

    Finally, you must build the standard applets: EditPythonPrefs, BuildApplet, etc. This is