Re: [Pyobjc-dev] Intel Transition update?
Brought to you by:
ronaldoussoren
From: Zachery B. <zb...@ur...> - 2005-12-19 21:31:39
|
On Dec 19, 2005, at 4:12 PM, Ronald Oussoren wrote: > On 19-dec-2005, at 20:40, Zachery Bir wrote: > >> On Dec 19, 2005, at 2:13 PM, Zachery Bir wrote: >> >>> As in, it will show Universal as the Architecture in Finder? If I >>> set AUTO_UNIVERSAL = True before any imports, Finder reports '--' >>> as the Architecture. >> >> Well, ignore this part. Finder was just slow to properly report >> the architecture. But the question still stands, is it supposed to >> report 'Intel, PowerPC' with that setting in setup.py? > > That's a bad explanation on my part. If you change the > AUTO_UNIVERSAL setting in the setup.py of PyObjC to True and then > rebuild PyObjC you'll end up with a universal binary for PyObjC > (and just PyObjC). Ah, that's much clearer :^) So, does this present a challenge when we want to build PyObjC on Panther in order to support older installations? Will Panther build universal binaries of PyObjC? *off to check* > You'll also want a universal binary of the py2app bootstrap > executable. To build that you'll have to do something like this: > > $ export CC="gcc -arch i386 -arch ppc" > $ cd $PYOBJC_ROOT # wherever you've extracted the PyObjC sources > $ cd source-deps/py2app/py2app/apptemplate > $ rm prebuild/main > $ python setup.py > > I haven't tested this procedure, but this should work. > > BTW. You'll also have to build universal binary versions of all > other extensions you're using. That should be easy enough for most > extensions (basically adding -arch i386 -arch ppc to > extra_compile_flags and extra_link_flags in setup.py), although > some setup.py files require more work. Thanks for all the info, this puts me much closer to understanding it all :^) Zac |