On Jan 16, 2006, at 3:21 PM, Michael Twomey wrote: > On 14/01/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: >> >> I wonder, though, if perhaps what's happening in the configuration >> that >> currently works, is that the path is being interpreted as "bundle >> relative" >> to the extension. This is fine and is really what we want, but >> I'm not >> sure that it can be done with older Mac OSes. I seem to recall that >> bundle-relative linking was added in 10.4? Or was it 10.3? I >> need to >> start actually *using* a Mac one of these days. :) >> > > I think it was in 10.3 (the MACOSX_DEPLOYMENT_TARGET affects this), > I'm pretty sure it was the "-undefined dynamic_lookup" which got > introduced, which had a big impact on shared libraries in bundles. I'm > not sure how this would affect the linking stuff above, it is "used to > allow any undefined symbols to be looked up dynamically at runtime" > according to the man page.
You are correct, MACOSX_DEPLOYMENT_TARGET=10.3 allows you to use - undefined dynamic_lookup. However, requiring Mac OS X 10.4 would allow you to use @loader_path [1], which would let you skip out on the chdir hack. [1] http://developer.apple.com/releasenotes/DeveloperTools/dyld.html -bob _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
