On Oct 25, 2006, at 9:58 AM, Norman Palardy wrote:
On Oct 25, 2006, at 4:56 AM, Jonathan Johnson wrote:
On Oct 25, 2006, at 12:23 AM, Norman Palardy wrote:
OK ... so I put calls to each function in their own method (still
in the same class) and see if that helps
Nope.
OK ... so take the two calls and put them in separate modules.
No luck.
After reading how dlopen and such work is this even possible
using those functions ?
And, since plugins contain dylibs how is this avoided if two
plugins have the same signature for a function ?
Depending on how you created your dylibs, you may not have two-
level namespaces enabled. This would be the first thing to look at.
Where in XCode is that setting ?
I can't seem to find it.
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 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.
HTH,
Jon
--
Jonathan Johnson
jonj at realsoftware dot com
REAL Software, Inc.
_______________________________________________
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>
|