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 19:14, Mark Dickinson wrote:
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. and a fresh checkout of the py3k branch from svn.python.org. I have a fairly limited goal: I want to create a universal (32-bit Intel/32-bit PPC) build on the 10.5/Intel machine, transfer it to the 10.4/PPC machine and then run the testsuite. (This has to do with making sure that a planned checkin is compatible with universal builds; see the (long) thread at http://mail.python.org/pipermail/python-dev/2009-April/088417.html ). What are the commands that I should execute on the Macbook? I tried: ./configure --with-universal-archs=32-bit --enable-framework --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.4 && make This seems to give me the right thing: Macintosh-4:py3k-short-float-repr dickinsm$ file python.exe python.exe: Mach-O universal binary with 2 architectures python.exe (for architecture ppc): Mach-O executable ppc python.exe (for architecture i386): Mach-O executable i386 Having done this, how do I package things up to transfer them to the iBook? What files need to be transferred? Mark _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig