[Python-checkins] CVS: python/dist/src/Mac/Demo building.html,1.30,1.31
Jack Jansen
jackjansen@users.sourceforge.net
2002年1月08日 15:03:48 -0800
Update of /cvsroot/python/python/dist/src/Mac/Demo
In directory usw-pr-cvs1:/tmp/cvs-serv7785/Python/Mac/Demo
Modified Files:
building.html
Log Message:
Updated for CW7 and Tcl/Tk 8.3.4. Also added a few other things
that were changed but not yet reflected in this document.
Index: building.html
===================================================================
RCS file: /cvsroot/python/python/dist/src/Mac/Demo/building.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -C2 -d -r1.30 -r1.31
*** building.html 2001年08月16日 14:10:56 1.30
--- building.html 2002年01月08日 23:03:45 1.31
***************
*** 13,16 ****
--- 13,19 ----
connection and probably quite some time too. <p>
+ Note that if you only want to build new extension modules you don't need to
+ build Python from source, see the <a href="#extending">note on extending Python</a>.<p>
+
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
***************
*** 21,25 ****
released after MacPython. The
<a href="http://www.cwi.nl/~jack/macpython.html">MacPython homepage</a> will
! hopefully have updated instructions in that case.
</blockquote>
--- 24,28 ----
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>
***************
*** 48,52 ****
<LI> You need MetroWerks CodeWarrior. The current distribution has
! been built with CodeWarrior Pro 6.1. Ordering information is
available on the <A HREF="http://www.metrowerks.com/">MetroWerks
homepage</A>. Building Python with MPW, Think/Symantec C or the OSX
--- 51,55 ----
<LI> You need MetroWerks CodeWarrior. The current distribution has
! been built with CodeWarrior Pro 7.1. Ordering information is
available on the <A HREF="http://www.metrowerks.com/">MetroWerks
homepage</A>. Building Python with MPW, Think/Symantec C or the OSX
***************
*** 57,62 ****
HREF="ftp://gusi.sourceforge.net/pub/gusi/">
ftp://gusi.sourceforge.net/pub/gusi/</A>. At
! the moment Python is built with a slightly modified version of GUSI
! 2.1.1, so it may be better to check the <A
HREF="http://www.cwi.nl/~jack/macpython.html">MacPython homepage</A>
for a GUSI that is most easily used for building Python.
--- 60,65 ----
HREF="ftp://gusi.sourceforge.net/pub/gusi/">
ftp://gusi.sourceforge.net/pub/gusi/</A>. At
! the moment Python is built with a modified version of GUSI
! with Carbon adaptations, so it may be better to check the <A
HREF="http://www.cwi.nl/~jack/macpython.html">MacPython homepage</A>
for a GUSI that is most easily used for building Python.
***************
*** 75,81 ****
<UL>
! <LI> Tcl and Tk are in a sad state on the Mac, the standard source distributions
! simply don't compile, so I have created a distribution especially for use
! with MacPython.
See the section on <A HREF="#tcltk">building Tcl/Tk Python</A>
below.
--- 78,83 ----
<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.
***************
*** 117,121 ****
Top-level-folder:
GUSI2
- GUSI2Carbon
imglibs
jpeg
--- 119,122 ----
***************
*** 132,139 ****
Build
...
! Tcl/Tk Folder
! tcl8.0
! tk8.0
! MoreFiles 1.4.3
</PRE>
--- 133,137 ----
Build
...
! Tcl/Tk Folder 8.3.4
</PRE>
***************
*** 145,149 ****
one. <p>
! First build GUSI, both the norla one and the Carbon variant.
<p>
--- 143,147 ----
one. <p>
! First build GUSI, both the normal one and the Carbon variant.
<p>
***************
*** 157,170 ****
<H2><A NAME="tcltk">Building Tcl/Tk</H2>
! The Tcl/Tk 8.3.0 source distribution does not work on the Mac. I have created
! an archive of the sources that I used to build _tkinter for MacPython,
! you can obtain this from <a
! href="ftp://ftp.cwi.nl/pub/jack/python/mac/tcltk830src-for-python.sit">
! ftp://ftp.cwi.nl/pub/jack/python/mac/tcltk830src-for-python.sit</a>. Only the
! libraries needed to build _tkinter for PPC have been fixed. <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>SimpleTk</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
--- 155,168 ----
<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
***************
*** 172,176 ****
Also note that the <code>_tkinter.ppc.slb</code> that is normally distributed
! in the <code>PlugIns</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).
--- 170,174 ----
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).
***************
*** 216,219 ****
--- 214,223 ----
on the Mac.
+ <DT> Lib
+ <DD> Machine-independent modules in Python.
+
+ <DT> Lib:lib-dynload
+ <DD> This is where the Classic and Carbon dynamically-loaded plugin modules live.
+
<DT> Objects
<DD> Machine-independent code for various object types. Most of these are
***************
*** 257,263 ****
<DT> Lib
! <DD> Mac-specific standard modules. The <code>toolbox</code> folder
contains modules specifically needed with various MacOS toolbox
! interface modules.
<DT> Modules
--- 261,267 ----
<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
***************
*** 286,291 ****
course).
! <DT> PlugIns
! <DD> This is where the Classic and Carbon dynamically-loaded plugin modules live.
<DT> Python
--- 290,300 ----
course).
! <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
***************
*** 313,317 ****
<H2>Building the PPC interpreter</H2>
! <em>This is different under 2.1. You are best off using the fullbuild.py
script, see <a href="#fullbuild">below</a>. </em><p>
--- 322,326 ----
<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>
***************
*** 346,350 ****
<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). <p>
<DT> Plugin projects
--- 355,362 ----
<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
***************
*** 382,408 ****
You are all set now, and should read the release notes and
<code>ReadMe</code> file from the <code>Mac</code> folder.
-
- <H2>Rebuilding <code>.exp</code> files</H2>
-
- Occasionally it may be necessary to rebuild your PythonCore <code>.exp</code>
- 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. <p>
-
- Rebuilding the .exp file is done by first both removing the file and removing the
- reference to it in the project (in the "config" section). Next, build PythonCore or
- PythonCoreCarbon.
- This will create a new .exp file, with the name <code>PythonCore.mcp.exp</code>.
- Rename this file to either <code>PythonCore.exp</code> or <code>PythonCoreCarbon.exp</code>
- and add this file back to the project. Next, edit ot to remove the references to
- the symbols <code>__initialize</code>, <code>__terminate</code>, <code>setjmp</code>,
- <code>longjmp</code>, <code>vec_longjmp</code>, <code>main</code> and <code>__ptmf_null</code>.
- They are all close together about halfway the file.
-
- Finally rebuild again. <p>
! 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.
<H2><a name="cvs">Using the CVS source archive</a></H2>
--- 394,399 ----
You are all set now, and should read the release notes and
<code>ReadMe</code> file from the <code>Mac</code> folder.
! Rebuilding .exp files is no longer needed since CodeWarrior 7.
<H2><a name="cvs">Using the CVS source archive</a></H2>
***************
*** 459,465 ****
(or, at the very least, link it before the normal C library).
! <LI> It is possible to build PPC extension modules without building a
! complete Python. The binary distribution installer can optionally install
! all the needed folders (the develop option). A template for a dynamic module can be found in
<code>xx.prj</code>.
--- 450,457 ----
(or, at the very least, link it before the normal C library).
! <LI> <a name="extending"></a>It is possible to build PPC extension
! modules without building a complete Python. The binary distribution
! installer can optionally install all the needed folders (the develop
! option). A template for a dynamic module can be found in
<code>xx.prj</code>.