Re: Delayed Framework Loading
Re: Delayed Framework Loading
- Subject: Re: Delayed Framework Loading
- From: Greg Guerin <email@hidden>
- Date: Fri, 12 Jun 2009 19:52:25 -0700
Dong Feng wrote:
The question rose by the first mail is to found a way making the
linker do the function address resolving (i.e. dynamic link)
automatically (as what achieved by link/weak-link the framework
directly) but still get the same lazy-initialization effect as what
achieved by CFURLCreateWithFileSystemPath().
That seems unlikely to me.
A library must be loaded in order to resolve the symbols it defines.
But when a library is loaded, it must also undergo initialization,
and part of that initialization involves executing initializer
functions. I don't see how you could get one without the other,
because it seems like an error condition to me (or incomplete
loading, which is a kind of error) if one is performed without the
other.
Read the section about the "DYLD_PRINT_INITIALIZERS" environment
variable here:
http://developer.apple.com/documentation/Darwin/Reference/ManPages/
man1/dyld.1.html
You might want to set that env-var when you're resolving your third-
party library, and see what functions get executed.
-- GG
_______________________________________________
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