From 8a6cdccf218880465366aeca59eb3de92d871dea Mon Sep 17 00:00:00 2001 From: Jack Jansen Date: Sun, 10 Sep 2000 12:02:28 +0000 Subject: Updated for 2.0b1 --- Mac/Demo/building.html | 147 +++++++++++++++++++++---------------------------- Mac/Demo/embed.html | 4 +- Mac/Demo/freezing.html | 3 +- Mac/Demo/using.html | 30 ++++++---- Mac/ReadMe | 90 +++++++++++++++--------------- 5 files changed, 126 insertions(+), 148 deletions(-) diff --git a/Mac/Demo/building.html b/Mac/Demo/building.html index e1a229e..1266154 100644 --- a/Mac/Demo/building.html +++ b/Mac/Demo/building.html @@ -7,11 +7,9 @@
This document explains how to build MacPython from source. This is -necessary if you want to write extension modules for 68K Python, and -is also necessary if you want to make modifications to the Python core. -Building Python is not something to be undertaken lightly, -you need a reasonable working -knowledge of the CodeWarrior development environment, a good net +necessary if you want to make modifications to the Python core. Building +Python is not something to be undertaken lightly, you need a reasonable +working knowledge of the CodeWarrior development environment, a good net connection and probably quite some time too.

The information density in this file is high, so you should probably @@ -43,49 +41,42 @@ at http://www.cwi.nl/~jack/macpython.html (which has up-to-date links to the other packages needed too) and possibly also from the standard python.org ftp -site. Everything you need is also included in the standard Python -source distribution, but the organization is different. Look in -directory Mac/mwerks/projects for the project files and -related stuff.
+site.
-An alternative is to check the sources straight out of the CVS +A better alternative is to check the sources straight out of the CVS repository, see below. Most of the packages mentioned here are also available through CVS. Check the section on CVS repository use below.

  • You need MetroWerks CodeWarrior. The current distribution has -been built with CodeWarrior Pro 4. Ordering information is +been built with CodeWarrior Pro 5.2. Ordering information is available on the MetroWerks homepage. Building Python with MPW or Think/Symantec C is probably impossible without major surgery. -
  • You need GUSI, the Grand Unified Socket Interface, by Matthias -Neeracher. The original CWGUSI is -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.
    +
  • You need GUSI version 2, the Grand Unified Socket Interface, by +Matthias Neeracher. The original GUSI is obtainable from +ftp://sunsite.cnlab-switch.ch/software/platform/macos/src/mw_c. At +the moment Python is built with a slightly modified version of GUSI +2.1.1, so it may be better to check the MacPython homepage +for a GUSI that is most easily used for building Python. +
    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 - +directory lib-src/GUSI2. As GUSI is moving to sourceforge +this info may be outdated by the time you read it so better check the +MacPython homepage, probably. The MacPython project files are configured to include a plethora of optional modules, and these modules need a number of extra packages. To use the project files as-is you have to -download these packages too. PPC and CFM68K Python have all such modules as +download these packages too. Python has all such modules as dynamically loaded modules, so if you don't need a certain package it -suffices to just refrain from builing the extension module. For static 68K -Python things are a bit more complicated: you have to edit the -interpreter project file to remove the reference to the module (and -the libraries it uses), and edit the Mac:mwerks:mwerks_nonshared_config.h -file to remove the USE_... line. Here are the locations for the various things +suffices to just refrain from builing the extension module. +Here are the locations for the various things you need: