Blame - Mac/Demo/building.html - platform/external/python/cpython3

blob: 036ff91b9897bada84a1a1216a36eac0cfeced71 [file] [log] [blame]

Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	1	<HTML>
				2	<HEAD>
				3	<TITLE>Building Mac Python from source</TITLE>
				4	</HEAD>
				5	<BODY>
				6	<H1>Building Mac Python from source</H1>
				7	<HR>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	8
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	9	This document explains how to build MacPython from source. This is
				10	necessary if you want to write extension modules for 68K Python, and
				11	currently also probably the easiest way to build PPC extension
				12	modules. Building Python is not something to be undertaken lightly,
				13	the process is not very streamlined so you need a reasonable working
				14	knowledge of the CodeWarrior development environment, a good net
				15	connection and probably quite some time too. <p>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	16
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	17	The information density in this file is high, so you should probably
				18	print it and read it at your leasure. Most things are explained only
				19	once (and probably in the wrong place:-). <p>
				20
				21	I am very interested in feedback on this document, contact me at <A
				22	HREF="mailto:jack@cwi.nl"><jack@cwi.nl></A> or send your
				23	comments to the <A
				24	HREF="http://www.python.org/sigs/pythonmac-sig/">Mac Python Special
				25	Interest Group</A>.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	26
				27	<H2>What you need.</H2>
				28
				29	The following things you definitely need:
				30
				31	<UL>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	32
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	33	<LI> You need a MacPython source distribution, of course. You can
				34	obtain one from <A
				35	HREF="ftp://ftp.cwi.nl/pub/jack/python/mac">ftp://ftp.cwi.nl/pub/jack/python/mac</A>,
				36	and possibly also from the standard <A
				37	HREF="ftp://ftp.python.org/pub/python/mac">python.org ftp
				38	site</A>. Everything you need is also included in the standard Python
				39	source distribution, but the organization is different. Look in
				40	directory <code>Mac/mwerks/projects</code> for the project files and
				41	related stuff.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	42
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	43	<LI> You need MetroWerks CodeWarrior. The current distribution has
				44	been built with version 9 of CodeWarrior. Ordering information is
				45	available on the <A HREF="http://www.metrowerks.com/">MetroWerks
				46	homepage</A>. You might still be able to build Python with MPW or
				47	Think/Symantec C but you are basically on your own.
				48
				49	<LI> You need GUSI, the Grand Unified Socket Interface, by Matthias
				50	Neeracher. The current distribution has been built with CWGUSI 1.7.2,
				51	obtainable from <A
				52	HREF="ftp://ftp.switch.ch/software/mac/src/mw_c">ftp://ftp.switch.ch/software/mac/src/mw_c</A>.
				53	It is possible to build a non-GUSI Python, see below.
				54
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	55	</UL>
				56
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	57	<A NAME="optional">The MacPython project files are configured to
				58	include a plethora of optional modules</A>, and these modules need a
				59	number extra packages. To use the project files as-is you have to
				60	download these packages too. PPC Python has all such modules as
				61	dynamically loaded modules, so if you don't need a certain package it
				62	suffices to just refrain from builing the extension module. For 68K
				63	Python things are a bit more complicated: you have to edit the
				64	interpreter project file to remove the reference to the module (and
				65	the libraries it uses). Here are the locations for the various things
				66	you need:
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	67
				68	<UL>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	69
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	70	<LI> Tcl and Tk can be obtained from <A
				71	HREF="ftp://ftp.smli.com/pub/tcl/mac/">ftp://ftp.smli.com/pub/tcl/mac/</A>.
				72	The current distributions, Tcl 7.5p1 and Tk 4.1p1 need a bit of work,
				73	see the section on <A HREF="#tcltk">building Tcl/Tk Python</A>
				74	below. Get the "full source" distribution, which includes MoreFiles.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	75
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	76	<LI> Waste, a TextEdit replacement written by Marco Piovanelli, <A
				77	HREF="mailto:piovanel@kagi.com"><piovanel@kagi.com></A>. Python
				78	was built using version 1.2, which you can obtain from <A
				79	HREF="ftp://rhino.harvard.edu/pub/dan/WASTE"><ftp://rhino.harvard.edu/pub/dan/WASTE></A>
				80	and various other places.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	81
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	82	<LI> JPEG library by the Independent JPEG Group. Python is still built
				83	using an archaic version of the library, version 4. It can be obtained
				84	from the <A HREF="ftp://ftp.cwi.nl/pub/jack/python/mac">
				85	ftp://ftp.cwi.nl/pub/jack/python/mac</A> directory, complete with CW8
				86	projects. If someone manages to build Python with the version 6
				87	library I would be grateful if they sent me the changes needed. The
				88	most recent JPEG library can always be obtained from <A
				89	HREF="ftp://ftp.uu.net/graphics/jpeg/">ftp://ftp.uu.net/graphics/jpeg/</A>.
				90
				91	<LI> The netpbm/pbmplus and libtiff libraries. The netpbm distribution
				92	(which includes libtiff) is generally available on Internet ftp
				93	servers. For Python pbmplus, an older incarnation of netpbm, is
				94	functionally identical to netpbm, since Python only uses the library
				95	and not the complete applications. A distribution with correct
				96	projects and library source only is available from, you guessed it, <A
				97	HREF="ftp://ftp.cwi.nl/pub/jack/python/mac">ftp://ftp.cwi.nl/pub/jack/python/mac</A>.
				98
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	99	</UL>
				100
				101	<H2>Setting Up</H2>
				102
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	103	Now that you have collected everything you should start with building
				104	the various parts. Everything is independent, with the single
				105	exception that Tcl and Tk depend on CWGUSI. If you don't want to fix
				106	access paths try to set things up as follows:
				107
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	108	<PRE>
				109	Top-level-folder:
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	110	CWGUSI
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	111	imglibs
				112	libjpeg
				113	pbmplus
				114	libtiff
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	115	MoreFiles 1.4.2 (not needed by Python, only by tcl/tk)
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	116	Python
				117	Tcl 7.5
				118	Tk 4.1
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	119	Waste 1.2 distribution (if you want waste)
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	120	</PRE>
				121
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	122	Now build all the libraries. In <code>CWGUSI</code> you build the
				123	projects <code>GUSI.68K.µ</code> and <code>GUSI.PPC.µ</code>, in
				124	<code>MoreFiles</code>, <code>libjpeg</code>, <code>pbmplus</code>
				125	and<code>libtiff</code> you build all projects. Tcl/tk is a special
				126	case, see below. Of course, if you are only interested in 68K you can
				127	skip building the PPC libraries and vice versa.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	128
				129	<H2><A NAME="tcltk">Building Tcl/Tk</H2>
				130
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	131	You need to make a minor organizational change to the Tcl/Tk
				132	distribution. The current instructions are for the
				133	<code>tcl7.5.1</code> and <code>tk4.1.1</code> distribution:
				134
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	135	<UL>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	136
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	137	<LI> Rename the <code>compat</code> folders to <code>(compat)</code>
				138	in both the Tcl and Tk folders.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	139
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	140	<LI> In the Tcl folder, move <code>strncasecmp.c</code> and
				141	<code>tclErrno.h</code> from <code>(compat)</code> to the main Tcl
				142	folder.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	143
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	144	<LI> Fix <code>dnr.c</code> as provided by MetroWerks by inserting
				145	<pre><code> #pragma ANSI_strict off </code></pre> at the
				146	beginning. The tcl library is built with strict ANSI on, and this file
				147	uses C++ style comments.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	148
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	149	<LI> If you want to build <code>SimpleTcl</code> and
				150	<code>SimpleTk</code> you will probably have to remove the references
				151	to <code>libmoto</code> from the project.
				152
				153	<LI> You are <EM>strongly</EM> advised to add a line
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	154	<pre><code>
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	155	#define USE_TCLALLOC 1
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	156	</code></pre>
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	157	somewhere at the beginning of <code>MW_TclHeader.pch</code>.
				158	As distributed, tcl and tk assume that malloc calls always succeed and
				159	use the resulting pointer without checking for <code>NULL</code>
				160	values. Needless to say, this wreaks havoc on a Macintosh.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	161
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	162	</UL>
				163
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	164	Build first the MoreFiles library, then the Tcl library, then
				165	SimpleTcl (test it by typing <code>ls -l</code> in the window you get)
				166	then the Tk library, then SimpleTk (which can again be tested with
				167	<code>ls -l</code>). If this all worked you are all set to try
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	168	building Python.
				169
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	170	<H2>Building Waste</H2>
				171
				172	You do not need to build the Waste libraries, as Python includes the
				173	source modules themselves. You have to make one modification,
				174	though. In file <code>ICCFMGlue.c</code> in folder <code>Minimal IC
				175	APIs</code>, add the following lines:
				176
				177	<blockquote><pre><code>
				178	#include <Gestalt.h>
				179	#include <Errors.h>
				180	</code></pre></blockquote>
				181
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	182	<H2>The organization of the Python source tree</H2>
				183
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	184	Time for a short break, while we have a look at the organization of
				185	the Python source tree. At the top level, we find the following
				186	folders:
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	187
				188	<DL>
				189	<DT> build.mac68k.stand
				190	<DD> This is where you will build 68K interpreters.
				191
				192	<DT> build.macppc.shared
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	193	<DD> This is where you build the PPC shared library, interpreter and
				194	applet framework.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	195
				196	<DT> build.macppc.stand
				197	<DD> This is where you build a nonshared PPC interpreter (optional).
				198
				199	<DT> Demo
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	200	<DD> Demo programs that are not Mac-specific. Some of these may not
				201	work, the file <code>README-Mac</code> has some details.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	202
				203	<DT> Extensions
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	204	<DD> Extensions to the interpreter that are not Mac-specific. Contains
				205	only the <code>img</code> extension in this distribution. Extensions
				206	are <em>not</em> built here, as they are on Unix, but incorporated in
				207	the core interpreter or built as plugin modules.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	208
				209	<DT> Grammar
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	210	<DD> The Python grammar. Included for reference only, you cannot build
				211	the parser on a Mac.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	212
				213	<DT> Include
				214	<DD> Machine-independent header files.
				215
				216	<DT> Modules
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	217	<DD> Machine-independent optional modules. Not all of these will work
				218	on the Mac.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	219
				220	<DT> Objects
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	221	<DD> Machine-independent code for various objects. Most of these are
				222	not really optional: the interpreter will not function without them.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	223
				224	<DT> Parser
				225	<DD> The Python parser (machine-independent).
				226
				227	<DT> PlugIns
				228	<DD> This is where you build the PPC dynamically-loaded plugin modules.
				229
				230	<DT> Python
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	231	<DD> The core interpreter. Most files are machine-independent, some
				232	are unix-specific and not used on the Mac.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	233
				234	<DT> Tools
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	235	<DD> Tools for python developers. Contains <code>modulator</code>
				236	which builds skeleton C extension modules and <code>bgen</code> which
				237	generates complete interface modules from information in C header
				238	files. There are some readme files, but more documentation is sorely
				239	needed.
				240
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	241	</DL>
				242
				243	All the mac-specific stuff lives in the <code>Mac</code> folder:
				244	<DL>
				245
				246	<DT> Compat
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	247	<DD> Unix-compatability routines. Some of these are not used anymore,
				248	since CWGUSI provides a rather complete emulation, but you may need
				249	these if you are trying to build a non-GUSI python.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	250
				251	<DT> Demo
				252	<DD> Mac-specific demo programs, some of them annotated.
				253
				254	<DT> Include
				255	<DD> Mac-specific but compiler-independent include files.
				256
				257	<DT> Lib
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	258	<DD> Mac-specific standard modules. The <code>toolbox</code> folder
				259	contains modules specifically needed with various MacOS toolbox
				260	interface modules.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	261
				262	<DT> Modules
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	263	<DD> Mac-specific builtin modules. Theoretically these are all
				264	optional, but some are rather essential (like
				265	<code>macmodule</code>). A lot of these modules are generated with
				266	<code>bgen</code>, in which case the bgen input files are included so
				267	you can attempt to regenerate them or extend them.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	268
				269	<DT> MPW
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	270	<DD> MPW-specific files. These have not been used or kept up-to-date
				271	for a long time, so use at your own risk.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	272
				273	<DT> mwerks
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	274	<DD> Mwerks-specific sources and headers. Contains glue code for
				275	Pythons shared-library architecture, a replacement for
				276	<code>malloc</code> and a directory with various projects for building
				277	variations on the Python interpreter. The <code>mwerks_*.h</code>
				278	files here are the option-setting files for the various interpreters
				279	and such, comparable to the unix command-line <code>-D</code> options
				280	to the compiler. Each project uses the correct option file as its
				281	"prefix file" in the "C/C++ language" settings. Disabling optional
				282	modules (for the 68K interpreter), building non-GUSI interpreters and
				283	various other things are accomplished by modifying these files (and
				284	possibly changing the list of files included in the project window, of
				285	course).
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	286
				287	<DT> Python
				288	<DD> Mac-specific parts of the core interpreter.
				289
				290	<DT> Resources
				291	<DD> Resource files needed to build the interpreter.
				292
				293	<DT> Scripts
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	294	<DD> A collection of various mac-specific Python scripts. Some are
				295	essential, some are useful but few are documented, so you will have to
				296	use your imagination to work them out.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	297
				298	<DT> Unsupported
				299	<DD> Modules that are not supported any longer but may still work with a little effort.
				300	</DL>
				301
				302	<H2>Building the 68K interpreter</H2>
				303
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	304	If you have all the optional libraries mentioned <A
				305	HREF="#optional">above</A> loaded buildin Python for 68K macs is a
				306	breeze: open the project in the folder <code>build.mac68k.stand</code>
				307	and build it. Do <em>not</em> run it yet, this will possibly result
				308	in a garbled preferences file. <p>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	309
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	310	First remove the <code>Python preferences</code> file from your
				311	preference folder, only if you had an older version of Python
				312	installed. (this is also what you do if you did not heed the last
				313	sentence of the preceeding paragraph). Next, move the interpreter to
				314	the main Python folder (up one level) and run it there. This will
				315	create a correct initial preferences file. You are now all set, and
				316	your tree should be completely compatible with a binary-only
				317	distribution. Read the release notes
				318	(<code>Relnotes-somethingorother</code>) and
				319	<code>ReadMeOrSuffer</code> in the <code>Mac</code> folder.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	320
				321	<H2>Building the PPC interpreter</H2>
				322
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	323	First you build the interpreter, core library and applet skeleton in
				324	folder <code>build.macppc.stand</code>. The order to build things is
				325	the following:
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	326
				327	<DL>
				328	<DT> PythonCoreRuntime
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	329	<DD> A modified version of the MetroWerks runtime library that is
				330	suitable for Pythons' shared library architecture. The sources all
				331	come from the MW distribution.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	332
				333	<DT> PythonCore
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	334	<DD> The shared library that contains the bulk of the interpreter and
				335	its resources. It is a good idea to immedeately put an alias to this
				336	shared library in the <code>Extensions</code> folder of your system
				337	folder. Do exactly that: put an <em>alias</em> there, copying or
				338	moving the file will cause you grief later.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	339
				340	<DT> PythonPPC
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	341	<DD> The interpreter. This is basically a routine to call out to the
				342	shared library. Because of the organization of GUSI it also contains
				343	the Gusi settings resource (together with a ResEdit template, so you
				344	can change the gusi settings should you feel like doing so). Do
				345	<em>not</em> run it yet, this will possibly result in a garbled
				346	preferences file. <p>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	347
				348	<DT> PythonApplet
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	349	<DD> The applet skeleton application. Very similar to
				350	<code>PythonPPC</code>, but it calls to a different entrypoint in the
				351	core library. The <code>mkapplet</code> script will copy this complete
				352	file, and add a <code>'PYC '</code> with the module to generate an
				353	applet. <p>
				354
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	355	</DL>
				356
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	357	After creating the alias to <code>PythonCore</code> you should move
				358	<code>PythonPPC</code> to the main Python folder. Next you remove any
				359	old <code>Python Preferences</code> file from the
				360	<code>Preferences</code> folder (if you had python installed on your
				361	system before) and run the interpreter once to create the correct
				362	preferences file. You should also make an alias to
				363	<code>PythonApplet</code> in the main Python folder. (again: making an
				364	alias is preferrable to copying or moving the file, since this will
				365	cause the correct file to be used if you ever rebuild
				366	PythonApplet). <p>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	367
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	368	Next, you have to build the extension modules in the
				369	<code>PlugIns</code> folder. Open each project and build it. After all
				370	the dynamically loaded modules are built you have to create a number
				371	of aliases: some modules live together in a single dynamic
				372	library. Copy or move the <code>MkPluginAliases.py</code> script from
				373	<code>Mac:scripts</code> to the main python folder and run it. <p>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	374
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	375	Finally, you must build the standard applets:
				376	<code>EditPythonPrefs</code>, <code>mkapplet</code>, etc. This is
				377	easiest done with the <code>fullbuild</code> script from
				378	<code>Mac:scripts</code>. Answer <em>no</em> to all questions except
				379	when it asks whether to build the applets. <p>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	380
				381	<BLOCKQUOTE>
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	382	Actually, the <code>fullbuild</code> script can be used to build
				383	everything, but you need a fully-functional interpreter before you can
				384	use it (and one that isn't rebuilt in the process: you cannot rebuild
				385	a running program). You could copy the 68K interpreter to a different
				386	place and use that to run fullbuild, or use the standalone PPC python
				387	for this. I tend to keep a standalone interpreter in a safe place for
				388	this use only.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	389	</BLOCKQUOTE>
				390
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	391	You are all set now, and should read the release notes and
				392	<code>ReadMeOrSuffer</code> file from the <code>Mac</code> folder.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	393
				394	<H2>Odds and ends</H2>
				395
				396	Some remarks that I could not fit in elsewhere:
				397
				398	<UL>
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	399
Jack Jansen	4c1e56c	1996-08-06 16:16:20 +0000	[diff] [blame^]	400	<LI> It may be possible to use the <code>PythonCore</code> shared
				401	library to embed Python in another program, if your program can live
				402	with using GUSI for I/O. Use PythonCore in stead of your C library
				403	(or, at the very least, link it before the normal C library). Let me
				404	know whether this works.
				405
				406	<LI> It is possible to build PPC extension modules without building a
				407	complete Python. Take the binary distribution, add folders
				408	<code>Include</code>, <code>Mac:Include</code> and
				409	<code>Mac:mwerks</code> from the source distribution and you should be
				410	all set. A template for a dynamic module can be found in
				411	<code>xxmodule.µ</code>.
Jack Jansen	8f2d802	1996-08-05 15:34:45 +0000	[diff] [blame]	412
				413
				414	<UL>
				415	</BODY>
				416	</HTML>