My purpose behind loading dynamic library is as follow:
My application runs as a deamon that loads the framework.
But the issue was that when my deamon starts, it loads the framework, but as soon as the its parent process get kills, the framework gets unloaded.
But my requirement is to get the framework remain loaded till my deamon is running.
So , one way can be to load the library after the parent process is killed and child gets created. So i thought to load the framework only after my child process is created.
On Thu, 2006-05-25 at 19:14 +0530, rohit dhamija wrote: > Hi Jonathon, > > Thanks for your reply. Also, it would be great if you could
> clarify/suggest below concerns too
You want to dynamically load the framework, using something similar to window's LoadLibrary() call? Is that correct?
It's certainly possible, and there are multiple ways of doing so, but
why? What does it buy you over weak linking and checking for function availability etc.?
See the documentation on dlopen(), CFBundle, NSBundle etc. for info on dynamically loading code.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
