Apple

On Jan 11, 2006, at 3:27 PM, Steve Mills wrote:

On Jan 11, 2006, at 17:03, Scott Tooker <email@hidden> wrote:

Unless you really NEED to run on a release before 10.3.4, don't

prebind your framework/app. It's just not worth the hassle.

Then why does the doc say I *should* prebind a framework (although it is a private framework internal to our app)?

"If you are developing a framework for versions of Mac OS X prior to 10.4, you should always build and ship it with prebinding enabled."

From <http://developer.apple.com/documentation/Performance/Conceptual/LaunchTime/Articles/Prebinding.html#//apple_ref/doc/uid/20001858>

Other than the small gap between "before 10.4" and "before 10.3.4," the two statements are in harmony. 10.3.4 and later have optimizations that make prebinding of frameworks (private and otherwise) less relevant. If you need to deploy pre-10.3.4, then go ahead and prebind; if you can require that your users upgrade to 10.3.9 or use Tiger, then prebinding of frameworks is "not worth the hassle."

References:
	>Re: prebinding framework (From: Steve Mills <email@hidden>)