[Python-checkins] python/dist/src/Mac/Demo building.html,1.33,1.33.4.1
jackjansen@users.sourceforge.net
jackjansen@users.sourceforge.net
Fri, 03 Jan 2003 15:53:55 -0800
Update of /cvsroot/python/python/dist/src/Mac/Demo
In directory sc8-pr-cvs1:/tmp/cvs-serv17970
Modified Files:
Tag: r23a1-branch
building.html
Log Message:
Updated for 2.3a1
Index: building.html
===================================================================
RCS file: /cvsroot/python/python/dist/src/Mac/Demo/building.html,v
retrieving revision 1.33
retrieving revision 1.33.4.1
diff -C2 -d -r1.33 -r1.33.4.1
*** building.html 30 Jan 2002 10:42:59 -0000 1.33
--- building.html 3 Jan 2003 23:53:52 -0000 1.33.4.1
***************
*** 1,11 ****
<HTML>
<HEAD>
! <TITLE>Building Mac Python from source</TITLE>
</HEAD>
<BODY>
! <H1>Building Mac Python from source</H1>
<HR>
! This document explains how to build MacPython from source. This is
necessary if you want to make modifications to the Python core. Building
Python is not something to be undertaken lightly, you need a reasonable
--- 1,11 ----
<HTML>
<HEAD>
! <TITLE>Building MacPython-OS9 from source</TITLE>
</HEAD>
<BODY>
! <H1>Building MacPython-OS9 from source</H1>
<HR>
! This document explains how to build MacPython-OS9 from source. This is
necessary if you want to make modifications to the Python core. Building
Python is not something to be undertaken lightly, you need a reasonable
***************
*** 24,31 ****
released after MacPython. The
<a href="http://www.cwi.nl/~jack/macpython.html">MacPython homepage</a> will
! hopefully have updated instructions in that case. These instructions are for CW7.
</blockquote>
! I am very interested in feedback on this document, send your
comments to the <A
HREF="http://www.python.org/sigs/pythonmac-sig/">Mac Python Special
--- 24,32 ----
released after MacPython. The
<a href="http://www.cwi.nl/~jack/macpython.html">MacPython homepage</a> will
! hopefully have updated instructions in that case. These instructions are for CW7,
! it is rumoured you may encounter some problems with newer versions of CodeWarrior.
</blockquote>
! I am interested in feedback on this document, send your
comments to the <A
HREF="http://www.python.org/sigs/pythonmac-sig/">Mac Python Special
***************
*** 78,86 ****
<UL>
- <LI> Tcl and Tk are somewhat less supported on the Mac than on Unix
- or Windows.
- See the section on <A HREF="#tcltk">building Tcl/Tk Python</A>
- below.
-
<LI> Waste, a TextEdit replacement written by Marco Piovanelli, <A
HREF="mailto:piovanel@kagi.com"><piovanel@kagi.com></A>. Python
--- 79,82 ----
***************
*** 133,137 ****
Build
...
- Tcl/Tk Folder 8.3.4
</PRE>
--- 129,132 ----
***************
*** 143,147 ****
one. <p>
! First build GUSI, both the normal one and the Carbon variant.
<p>
--- 138,142 ----
one. <p>
! First build GUSI, the Carbon variant.
<p>
***************
*** 153,185 ****
case, see below.
- <H2><A NAME="tcltk">Building Tcl/Tk</H2>
-
- Tkinter has been built with Tcl/Tk 8.3.4. Load the Mac source distribution
- from the tcl sourceforge site and build it. Build with CW7, but you will
- need CW6 to build the MDEF resource (or copy it from a binary
- installation). As of this writing the projects are CW6, so they need
- massaging to build with CW7, but this is a lot less work than applying
- all the workarounds for CW6 that the build instructions give. <P>
-
- Note that if you use a different release of Tcl and Tk than the ones
- I have used you may have to adapt the Python <code>tkresources.rsrc</code> file.
- This is easiest done by building <code>Tk8.3.shlb</code> and copying the TEXT, ICON
- and CRSR resources from it to <code>tkresources.rsrc</code>. This allows
- the <code>_tkinter</code> module to work without an installed Tk/Tcl on your
- machine. <P>
-
- Also note that the <code>_tkinter.ppc.slb</code> that is normally distributed
- in the <code>lib-dynload</code> folder is the one from the Imaging extension,
- which has some extra features needed by PIL (and which features should not
- hinder normal operation).
-
- </UL>
-
- Build first the Tcl library, then
- SimpleTcl (test it by typing <code>ls -l</code> in the window you get)
- then the Tk library, then SimpleTk (which can again be tested with
- <code>ls -l</code>). If this all worked you are all set to try
- building Python.
-
<H2>The organization of the Python source tree</H2>
--- 148,151 ----
***************
*** 213,217 ****
<DT> Lib:lib-dynload
! <DD> This is where the Classic and Carbon dynamically-loaded plugin modules live.
<DT> Objects
--- 179,187 ----
<DT> Lib:lib-dynload
! <DD> This is where the dynamically-loaded plugin modules live.
!
! <DT> Lib:plat-mac
! <DD> This is where most of the Mac-specific modules live. The modules here
! are available both in MacPython-OS9 and MacPython-OSX.
<DT> Objects
***************
*** 236,240 ****
</DL>
! All the mac-specific stuff lives in the <code>Mac</code> folder:
<DL>
<DT> Build
--- 206,210 ----
</DL>
! The mac-specific stuff lives in the <code>Mac</code> folder:
<DL>
<DT> Build
***************
*** 242,246 ****
libraries, shared libraries, executables and plugin modules. All the
resulting binaries, except for intermedeate results, are deposited in
! the toplevel folder or the Mac:PlugIns folder (for plugin modules).
<DT> Compat
--- 212,216 ----
libraries, shared libraries, executables and plugin modules. All the
resulting binaries, except for intermedeate results, are deposited in
! the toplevel folder or the :Lib:lib-dynload folder (for plugin modules).
<DT> Compat
***************
*** 256,262 ****
<DT> Lib
! <DD> Mac-specific standard modules. The <code>Carbon</code> package
! contains modules specifically needed with various MacOS toolbox
! interface modules, both for Carbon and classic PPC, despite the name.
<DT> Modules
--- 226,231 ----
<DT> Lib
! <DD> MacPython-OS9 specific standard modules which are not shared with
! MacPython-OSX.
<DT> Modules
***************
*** 286,295 ****
<DT> OSX
! <DD> Specific to unix-Python (also known as MachoPython) on OSX, not used
! by MacPython.
<DT> OSXResources
! <DD> Specific to unix-Python (also known as MachoPython) on OSX, not used
! by MacPython.
<DT> Python
--- 255,262 ----
<DT> OSX
! <DD> Specific to MacPython-OSX, not used by MacPython-OS9.
<DT> OSXResources
! <DD> Specific to MacPython-OSX, not used by MacPython-OS9.
<DT> Python
***************
*** 317,335 ****
<H2>Building the PPC interpreter</H2>
- <em>This is different since 2.1. You are best off using the fullbuild.py
- script, see <a href="#fullbuild">below</a>. </em><p>
! First you optionally build the external libraries with buildlibs.prj. Next,
! the projects for
! interpreter and core library are linked together, so
! building the PythonInterpreterClassic and/or PythonInterpreterCarbon target
! in <code>PythonInterpreter.prj</code>
! will result in everything being built. The result, however, is an "Application
! template", (filetype Atmp). If you don't use fullbuild you can manually
! turn either of these into an interpreter by copying it to PythonInterpreter
! and setting the filetype to APPL (with ResEdit or some such). <p>
! Fullbuild does this for you, and the Atmp files is also how ConfigurePythonCarbon
! and ConfigurePythonClassic work their magic. <p>
You will get about 100 warnings on "missing prototype" for the various module init
--- 284,305 ----
<H2>Building the PPC interpreter</H2>
! First you optionally build the external libraries with buildlibs.prj. <p>
! Then, the <code>fullbuild</code> 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 interpreter to a different
! place and use that to run fullbuild. The <code>PythonStandSmall.prj</code>
! project builds an interpreter that is suited to this, and it can also come
! in handy if you need to debug things (which is easier in a static program). <p>
!
! In case you want to build by hand, or in case the <code>fullbuild</code>
! script does not work, here is a breakdown of the various projects. <p>
!
! The projects for interpreter and core library are linked together, so
! building the PythonInterpreter target
! in <code>PythonInterpreter.prj</code>
! will result in the whole core being built, but not the extension modules. <p>
You will get about 100 warnings on "missing prototype" for the various module init
***************
*** 337,341 ****
override functions from MSL, ignore these too. <p>
! For completeness sake here is a breakdown of the projects:
<DL>
--- 307,311 ----
override functions from MSL, ignore these too. <p>
! Here is a breakdown of the projects:
<DL>
***************
*** 343,347 ****
<DT> PythonCore
<DD> The shared library that contains the bulk of the interpreter and
! its resources. It has targets for PythonCore and PythonCoreCarbon.
It is a good idea to immedeately put an alias to this
shared library in the <code>Extensions</code> folder of your system
--- 313,317 ----
<DT> PythonCore
<DD> The shared library that contains the bulk of the interpreter and
! its resources.
It is a good idea to immedeately put an alias to this
shared library in the <code>Extensions</code> folder of your system
***************
*** 353,361 ****
<DT> PythonInterpeter
<DD> The interpreter. This is basically a routine to call out to the
! shared library. Unlike in previous releases the same program is used for
! creating applets (for which formerly PythonApplet was used). There are 4 targets
! in here: two for the classic and carbon templates (which are normally used, and
! converted to PythonInterpreter by the ConfigurePython* applets) and two
! for PythonInterpreter in it's classic and carbon version.<p>
<DT> Plugin projects
--- 323,327 ----
<DT> PythonInterpeter
<DD> The interpreter. This is basically a routine to call out to the
! shared library. <p>
<DT> Plugin projects
***************
*** 379,394 ****
BuildApplet. <p>
- <BLOCKQUOTE>
- <a name="fullbuild"></a>
- The <code>fullbuild</code> 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 interpreter to a different
- place and use that to run fullbuild. The <code>PythonStandSmall.prj</code>
- project builds an interpreter that is suited to this, and it can also come
- in handy if you need to debug things (which is easier in a static program). <p>
-
- </BLOCKQUOTE>
-
You are all set now, and should read the release notes and
<code>ReadMe</code> file from the <code>Mac</code> folder.
--- 345,348 ----
***************
*** 412,425 ****
conversion". <p>
! <blockquote>
! There is one group of people for whom MacCVS is not the best choice: people with
! checkin rights to the Python repository. You will have to use MacCVS Pro
! (completely unrelated) from www.maccvs.org, because it has working SSH support.
! </blockquote>
!
! It is a good idea to disable Quicktime Exchange in the Quicktime
! control panel. Quicktime Exchange will magically map some extensions to
! filetypes, and this can seriously hinder you if, for instance, <code>.bmp</code>
! is not a Windows bitmap file. <p>
The Python sources are checked out from the main
--- 366,373 ----
conversion". <p>
! It is a good idea to disable Quicktime Exchange in the Quicktime control
! panel if you are on OS9 or before. Quicktime Exchange will magically map
! some extensions to filetypes, and this can seriously hinder you if, for
! instance, <code>.bmp</code> is not a Windows bitmap file. <p>
The Python sources are checked out from the main
***************
*** 436,440 ****
it is probably a good idea to first build <code>PythonStandSmall.prj</code>,
which builds a fairly minimal interpreter, and then follow the
! <a href="#fullbuild">fullbuild instructions</a>.
<H2>Odds and ends</H2>
--- 384,388 ----
it is probably a good idea to first build <code>PythonStandSmall.prj</code>,
which builds a fairly minimal interpreter, and then follow the
! fullbuild instructions</a>.
<H2>Odds and ends</H2>
***************
*** 447,451 ****
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).
<LI> <a name="extending"></a>It is possible to build PPC extension
--- 395,400 ----
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). Ask for help
! on PythonMac-SIG if you have problems with this.
<LI> <a name="extending"></a>It is possible to build PPC extension