[Pythonmac-SIG] compiling MacPython

Martin Miller mmiller@adobe.com
Wed, 10 Apr 2002 10:40:00 -0700


Hi Matt, 

I think you do need Codewarrior 7. I personally have not had the
problems you describe when building MacPython 2.2 from the source
distribution using CW7.

The MacPython webpage at <http://www.cwi.nl/~jack/macpython.html> says
the following:

In the "Current distribution" section:
> Note 4: The extension module developer package in the MacPython 
> distribution assumes you use Metrowerks CodeWarrior Pro 7. If you
> have CodeWarrior 5.3 you should get this patch provided by Tom Loredo. 
> patch <http://www128.pair.com/loredo/macpython/CW5%20for%20MacPy2.2.sit.hqx>

and, in the "Source distributions" section:
> The source distribution has built with CodeWarrior Pro 7. It is, 
> however, strongly suggested that if you want to contribute actively 
> to MacPython development you get source access through the public 
> CVS repository (see below), as this will ensure that you are always
> working with the most recent version of the sources. 

Hope this helps,
-Martin


========================================= 
Matt Sykes <mattmsykes@yahoo.co.uk> wrote:
> 
> Apologies if I am sounding naive; I am new to this SIG.
> 
> The link to the MacPython SIG archives at
> http://www.python.org/sigs/pythonmac-sig/ is broken so I can't search
> to see if this is a FAQ.
> 
> I am unable to compile MacPython (2.2 and the brand-new 2.2.1) from
> source with Codewarrior 6.1.  Do I need Codewarrior 7?  Are the docs
> that mention Codewarrior 6.1 out of date?
> 
> When I open PythonCore.mcp it asks me if I wish to convert the file to
> a newer format.  After I do this, it appears the project is *hosed*.
> I am unable to add or remove files from the project, among other
> problems which appear to be obvious bugs from the conversion.
> 
> GUSI compiles without trouble for all targets.
> 
> Thanks,
> --Matt