On Oct 25, 2006, at 9:32 AM, Jonathan Johnson wrote:
In Xcode 2.4... actually, nevermind. It appears that it's no longer
obvious how to turn this feature off, so you probably have it on
(which it is by default).
I'm only using 2.3
Guess I should update :)
It looks like the man page for ld says
-flat_namespace or -force_flat_namespace
in the Other Linker Flags will force a flat name space
I did find lots of message between you and Chris Espinosa about
this but darned if I could find the setting :)
Well, here's the issue. It turns out this is the problem. We use
NSAddImage and NSLookupSymbolInImage because dyld isn't available
in anything prior to 10.3. NSAddImage has no notion of adding an
image to a private namespace, even if two level namespaces are
used. So, whichever library loads the symbol first will be used for
the rest of the run.
We can use dyld on 10.3 and higher though, so if possible, please
file a report against this. One workaround might be to package the
dylib into a bundle and declare against the bundle. This should work.
Not sure exactly what the wording of such a bug report might be though ?
"Can't properly call functions loaded from different dylibs on OS X <
10.3 " or something like that ?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
