Re: Dylib and parent application symbol access
Re: Dylib and parent application symbol access
- Subject: Re: Dylib and parent application symbol access
- From: Wade Tregaskis <email@hidden>
- Date: Mon, 09 Jan 2012 18:05:25 -0800
> The dylib project is intended to be an SDK so 3rd parties can write their own plugin.
> The project has to be stand alone and somehow link to the APP.
Then your library is essentially a framework, for the purposes of this discussion. So the question is why you have your library depending on your app? The typical pattern is to have your app call into the plug-in library, registering callbacks or similar if necessary.
Note that you can get away with a lot thanks to the dynamic nature of Objective-C. Can you use ObjC classes and methods instead of C functions & constants?
There's almost certainly a way to do things the way you're insisting, but you'll be working against the flow the entire time. The closer you can follow the prescribed patterns, the easier it'll be.
_______________________________________________
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