[Pyobjc-dev] 10.6: Twisty maze of build issues
Brought to you by:
ronaldoussoren
From: Aahz <aa...@py...> - 2010-01-12 21:36:25
|
I'm building an app on 10.5, trying to support Intel 10.4, 10.5, 10.6. Currently I'm using a combination of PyObjC 1.4 (originally to support PPC 10.4) and PyObjC 2.2b2 to capture FSEvents in a subprocess. When 10.6 was released, my app crashed. Then Apple delivered some updates and my app started working in mid-November. Now apparently Apple has put out new updates and my app is crashing again. I am moderately sure that I can fix this with some combination of build changes, but I'd like some guidance to avoid thrashing around. I'm using the python.org build for Python 2.6.4. I've tried upgrading to PyObjC 2.2, but that breaks on 10.5 with ImportError: dlopen(/Users/aahz/Library/Python/2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/_objc.so, 2): Library not loaded: /usr/lib/libxml2.2.dylib Reason: Incompatible library version: _objc.so requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0 Should I try just building PyObjC 2.2 from source? I tried updating macports before I realized that this was the system libxml. AFAICT, PyObjC 2.2b2 is crashing on from Foundation import NSAutoreleasePool, NSMutableArray, NSString in objc._bridgesupport._parseBridgeSupport() with "ValueError: Unknown typestr". Assuming the line number matches the source, that's objc.parseBridgeSupport(data, globals, frameworkName, *args, **kwds) OTOH, the app built with PyObjC 1.4 is crashing with USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER and I'm not sure where. Any clues? -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair |