Re: Symbol Sharing between Dylibs (and how to prevent it)
Re: Symbol Sharing between Dylibs (and how to prevent it)
- Subject: Re: Symbol Sharing between Dylibs (and how to prevent it)
- From: "Jonathan Johnson" <email@hidden>
- Date: Thu, 31 Aug 2006 14:02:48 -0500
On 8/31/06, Chris Espinosa <email@hidden> wrote:
This is because dylibs default to global namespace and bundles (and plugins)
default to "two-level namespace." You can easily set any dylib to two-level
namespace
In my original reply, I noted that I have this option turned on
already. In fact, our compiler specifically checks for this attribute,
otherwise plugins wouldn't have worked at all. However, the symbols
that dyld automatically resolved didn't seem to respect which image
the requester was in. Our call to NSLookupSymbolInImage resolved the
correct symbol -- before enabling two-level namespaces several years
ago, this wouldn't work because a REALPluginMain entrypoint had
already been introduced in the global namespace.
From everything I tried, the only solution that worked was using a
Bundle rather than a dynamic library.
-Jon
--
Jonathan Johnson
REAL Software, Inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden