[Pyobjc-dev] Intel worries
Brought to you by:
ronaldoussoren
From: Diez B. R. <de...@we...> - 2007-02-03 18:23:38
|
Hi, I'm sorry but I don't know about a better place to ask. I've just started toying around with PyObjc and my new MacBookPro. Everything is fine, and I began to explore the OpenCV library again - first, creating an Intel-only build + a Objective-C wrapper library. I had that code running under PPC, and it was easy as cake to make it compile under Intel. However, when loading my i386-only frameworks, objc.loadBundle puked on me. I had to recompile everything using i386,ppc as architecture. I'm fairly ok with that - yet I wonder: does that mean that if one binary is fat, all have to be? Of course that is fine. But when I do a file /Users/deets/Projects/CameraCalibrator/build/CameraCalibrator.app/Contents/MacOS/CameraCalibrator where CameraCalirator is a py2app-generated executable, it tells me it is a "Mach-O executable ppc". So - does that mean that the ppc code is actually used, in some slowing-down simulation? If so, is there a way to make that py2app create an intel binary? I'm sorry if these are stupid questions - this is my first encounter with that topic at all. Thanks, Diez |