diff options
| author | Jack Jansen <jack.jansen@cwi.nl> | 1998-02-25 15:40:35 (GMT) |
|---|---|---|
| committer | Jack Jansen <jack.jansen@cwi.nl> | 1998-02-25 15:40:35 (GMT) |
| commit | a2139fef94c0f94bb897a62f4e2c53f40eb40cc4 (patch) | |
| tree | 7a5b1646a79fb78449c298b79432da1c90ec65fa /Mac/Demo/plugins.html | |
| parent | b92dce38e7834dcde4f450c89da1c10f81a6d1a0 (diff) | |
| download | cpython-a2139fef94c0f94bb897a62f4e2c53f40eb40cc4.zip cpython-a2139fef94c0f94bb897a62f4e2c53f40eb40cc4.tar.gz cpython-a2139fef94c0f94bb897a62f4e2c53f40eb40cc4.tar.bz2 | |
Added (minimal) documentation on how to build standalone applications
with Python.
Updated various things (versions of libraries used, urls).
Diffstat (limited to 'Mac/Demo/plugins.html')
| -rw-r--r-- | Mac/Demo/plugins.html | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/Mac/Demo/plugins.html b/Mac/Demo/plugins.html index 7d43e72..368f50b 100644 --- a/Mac/Demo/plugins.html +++ b/Mac/Demo/plugins.html @@ -26,8 +26,7 @@ Next, you need a <A HREF="http://www.python.org/python/Sources.html">python source distribution</A>. For PowerPC and cfm68k development you can actually get by without a full source distribution, using the Development -distribution (if I have gotten around to putting it together by the time -you read this). You'll also need a functional python interpreter, and +distribution. You'll also need a functional python interpreter, and the Modulator program (which lives in <CODE>Tools:Modulator</CODE> in the standard source distribution). You may also find that Guido's <A HREF="http://www.python.org/doc/ext/ext.html">Extending and embedding @@ -190,9 +189,9 @@ language" section of the MW preferences dialog, it will probably be Make the new interpreter and check that you can import the module, see the methods (with "dir(interslip)") and call them. <p> -<H2>Creating a PowerPC plugin module</H2> +<H2>Creating a plugin module</H2> -For PowerPC development you could follow the same path, but it is +For PowerPC or cfm68k development you could follow the same path, but it is actually a better idea to use a dynamically loadable module. The advantage of dynamically loadable modules is that they are not loaded until a python program actually uses them (resulting in less memory @@ -211,6 +210,12 @@ of adjustments to the preferences: <UL> <LI> in PPC target, set the output file name to "interslipmodule.pcc.slb", <LI> in cfm68k target set the output file name to "interslipmodule.cfm68k.slb". +<LI> if you are working without a source distribution (i.e. with a normal +binary distribution plus a development distribution) you will not have +a file <code>PythonCore</code>. The installation process has deposited this +file in the System <code>Extensions</code> folder under the name +<code>PythonCore <i>version</i></code>. Add that file to the project, replacing +<code>PythonCore</code>. </UL> Next, compile and link your module, fire up python and do the same tests as for 68K python. <p> |