Thank you, Skip and Ronald. Together with Ned's information from the python-dev
thread, I managed to build a non-framework universal build on Intel, transfer
a tarball to PPC and get it to run the testsuite.
For future reference, the steps that worked were:
export MACOSX_DEPLOYMENT_TARGET=10.3
.
Mark,
If you're only testing I'd lose the --enable-framework bit and create
a regular unix install. That way you won't mess up any regular python
install's you have (such as Python.org binary install), and you can
just copy the sys.prefix to the other machine.
Ronald
On 14 Apr, 2009, at
Mark> Having done this, how do I package things up to transfer them to
Mark> the iBook? What files need to be transferred?
If this is a one-time thing I would use brute force and tar up the entire
source directory and put it over on your g4.
Skip
___
This question has probably been asked and answered before,
but I've failed to find anything in the archives.
What's the 'correct' way to create a universal build of Python?
Specifically, I have two machines:
(1) a Macbook Pro (Core 2 Duo) running OS X 10.5, and
(2) an iBook G4 running OS X 10.4.
A better way to define such accessors is like so:
@objc.accessor
def objectInFooAtIndex_(self, index):
pass
This should deduce the right method signature based on the method
name. I guess this needs better documentation :-(
Ronald
On 13 Apr, 2009, at 19:00, David Hain wrote:
