On Jun 2, 2006, at 7:54 AM, Luc Heinrich wrote:
> This may probably be a py2app specific question but since I'm using
> the one bundled with PyObjC I figure I'd just ask here first.
> I'm producing a standalone PyObjC application which bundles a custom
> Python installation (2.4.3 from DarwinPorts) and this application
> must launch a subprocess using the embedded python executable, which
> doesn't seem to work across different machines.
> A quick glance at the output of otool shows that the embedded python
> executable still references the locally installed Python framework
> and therefore will produce an error when launched on a different
> % otool -L MyApp.app/Contents/Frameworks/Python.framework/Versions/
> (compatibility version 2.4.0, current version 2.4.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 88.1.5)
> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
> version 7.4.0)
> /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
> version 1.0.0)
> Notice the /opt/local line. I have tried with a different version of
> py2app (0.2) but the problem remains.
> I'd love to know what I am doing wrong... :)
Nothing, py2app's support for spawning subprocesses is flaky at best.