The information density in this file is high, so you should probably print it and read it at your leasure. Most things are explained only once (and probably in the wrong place:-).
I am very interested in feedback on this document, send your comments to the Mac Python Special Interest Group.
Mac/mwerks/projects
for the project files and
related stuff. Python:Mac:GUSI-mods
. 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
Mac:mwerks:mwerks_nonshared_config.h
file to remove the USE_...
line. Here are the locations for the various things
you need:
lib-src/gdbm
.
lib-src/jpeg
.
lib-src/netpbm
, etc. The only gotcha is that libtiff lives in
lib-src/netpbm/libtiff
, for historical reasons.
Top-level-folder: CWGUSI imglibs jpeg netpbm libtiff zlib png gdbm Python Tcl/Tk Folder tcl8.0 tk8.0 MoreFiles 1.4.3 Waste 1.3 distribution (if you want waste)If your setup of the libraries is exactly the same as mine (which is not very likely, unless you happen to work from the same CVS repository) you can use the project
buildlibs.prj
in the
:Mac:build.mac
folder to build all needed libraries in one
fell swoop, otherwise you will have to build the libraries one by
one. First build GUSI. If you didn't get the python-specific GUSI you have to move the files from the "CWGUSI-mods" to the right place in the CWGUSI distribution folder. Build the MSL version for your platform (ppc, 68k, cfm68k).
Note: always rebuild the CWGUSI libraries, even if you have checked them out from the CVS repository.
Next, in
MoreFiles
, libjpeg
, pbmplus
,
zlib
, libpng
, gdbm
,
andlibtiff
you build all projects. Usually the projects are in "mac"
subfolders, sometimes they are in the main folder. Tcl/tk is a special
case, see below. Of course, if you are only interested in one of
static 68K, CFM68K or PPC you can skip building the other libraries.
tkresources.rsrc
file.
This is easiest done by building SimpleTk
and copying the TEXT, ICON
and CRSR resources from it to tkresources.rsrc
. This allows
the _tkinter
module to work without an installed Tk/Tcl on your
machine.
ls -l
in the window you get)
then the Tk library, then SimpleTk (which can again be tested with
ls -l
). If this all worked you are all set to try
building Python.
README-Mac
has some details.
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).
modulator
which builds skeleton C extension modules and bgen
which
generates complete interface modules from information in C header
files. There are some readme files, but more documentation is sorely
needed.
Mac
folder:
toolbox
folder
contains modules specifically needed with various MacOS toolbox
interface modules.
macmodule
). A lot of these modules are generated with
bgen
, in which case the bgen input files are included so
you can attempt to regenerate them or extend them.
malloc
and a directory with various projects for building
variations on the Python interpreter. The mwerks_*.h
files here are the option-setting files for the various interpreters
and such, comparable to the unix command-line -D
options
to the compiler. Each project uses the correct option file as its
"prefix file" in the "C/C++ language" settings. Disabling optional
modules (for the 68K interpreter), building non-GUSI interpreters and
various other things are accomplished by modifying these files (and
possibly changing the list of files included in the project window, of
course).
If you were previously running another copy of this Python release,
from a binary installer for instance, you should
first remove the Python XXX preferences
file from your
preference folder. Next, run the interpreter, in the toplevel folder. This will
create a correct initial preferences file. You are now all set, and
your tree should be completely compatible with a binary-only
distribution. Read the release notes
(Relnotes-somethingorother
) and
ReadMe
in the Mac
folder.
If something goes wrong you may end up with a garbled preferences file. Removing it from the system folder and running Python once again will re-create it.
PythonEngine.prj
will result in everything being built. The
resulting applications and fat shared library are deposited in the main
Python folder. Finally, you build all the plugins with the plugins.prj project.
For completeness sake here is a breakdown of the projects:
Extensions
folder of your system
folder. Do exactly that: put an alias there, copying or
moving the file will cause you grief later if you rebuild the library and
forget to copy it to the extensions folder again. The InstallPython applet
will also do this, along with creating the plugin aliases.
Plugins.prj
project tries to build them all, but is known to be flakey under CW Pro 4.
PythonCore
you remove any old
Python XXX Preferences
file from the Preferences
folder
(if you had python installed on your system before) and run the interpreter once
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 (but see the gotcha above).
Finally, you must build the standard applets:
EditPythonPrefs
, BuildApplet
, etc. This is
easiest done with the fullbuild
script from
Mac:scripts
.
Actually, theYou are all set now, and should read the release notes andfullbuild
script can be used to build everything, but you need a fully-functional interpreter before you can use it (and one that isn't rebuilt in the process: you cannot rebuild a running program). You could copy the 68K interpreter to a different place and use that to run fullbuild, or use the standalone PPC python for this. I tend to keep a standalone interpreter in a safe place for this use only.
ReadMe
file from the Mac
folder.
.exp
files for PPC and CFM68K.exp
file, a file that controls which symbols are exported by your PythonCore
shared library. Rebuild it if you get unexpected undefined symbols when you
are building a plugin module.
Rebuilding the .exp file is done by first removing the file and removing the
reference to it in the project (in the "config" section). Next, build PythonCore.
This will create a new .exp file. Edit this file to remove the references to
the symbols __initialize
, __terminate
, setjmp
,
longjmp
, main
and (for PPC) __ptmf_null
or (for
CFM68K) __start
and dummy_init_routine
.
Next, add the .exp file to the project
again and rebuild PythonCore.
This rather convoluted procedure is needed to ensure that plugin modules don't accidentally link with those entrypoints from PythonCore, which will not work because those routines have to be in the same code fragment as they are used from.
The CVS client of choice is Alexandre Parenteau's MacCVS. It can be obtained through the WinCVS homepage. MacCVS uses Internet Config to set file types correctly based on the filename extension. In the maccvs preferences you should also set (in the "binary files" section) "use mac encoding: applesingle" and (in the "text files" section) "use ISO latin 1 conversion".
The machine-independent Python sources are checked out from the main
Python CVS archive, see the Source access via
CVS page for details. When you check the sources out you will get
something like Python:dist:src
, and under that the
Modules
, Lib
, etc hierarchy. The
src
folder should be renamed to Python
, and
is what this document refers to as the "toplevel Python folder".
Next, within the toplevel Python folder, you check out the mac-specific sources in a Mac folder. The CVS path to use can be found at the MacPython homepage. Finally, you check out the external libraries needed in the parent of the Python folder. The CVS path for these libraries is also mentioned at the MacPython homepage.
Neither of the pages mentioned above contains the passwords for the CVS sites, for obvious reasons, but they do contain instructions on how to obtain the passwords.
PythonCore
shared
library to embed Python in another program, if your program can live
with using GUSI for I/O. Use PythonCore in stead of your MSL C library
(or, at the very least, link it before the normal C library). Let me
know whether this works.
xx.prj
.
MSL AppRuntime.Lib
runtime library (with properly set CFM
initialization and termination routines). PythonCore uses MSL Runtime.Lib
,
which is really intended for standalone programs but which we fool into working by
providing a dummy main program.
It is linked statically into PythonCore (and exported to the applications and plugins)
so we do not have to distribute yet another shared library. Plugin modules use
MSL ShlibRuntime.Lib
(not the dropin runtime: modules are never unloaded)
and obtain the rest from PythonCore. PythonCore uses a
non-standard initialization entry point, __initialize_with_resources
, to
be able to obtain resources from the library file later on. Plugins can do the same
(_tkinter does) or use the standard __initialize
entry point.