Re: Shared frameworks, not in an app wrapper (Was: Frameworks in the app wrapper)
Re: Shared frameworks, not in an app wrapper (Was: Frameworks in the app wrapper)
- Subject: Re: Shared frameworks, not in an app wrapper (Was: Frameworks in the app wrapper)
- From: Bill Bumgarner <email@hidden>
- Date: Thu, 19 Dec 2002 13:07:23 -0500
On Thursday, Dec 19, 2002, at 12:08 US/Eastern, Phil Barrett wrote:
Maybe weak-linking is the answer - allow the app to start, discover
frameworks are missing, berate the user, find them, load them and
continue.
Can someone-- Apple?-- point to, create or post an example of how to do
this? There are a lot of folks in the development community that are
in the same boat.
Then again, maybe we need to return to the old NeXT way of static
linking
everything. Great runtime performance, but it uses a lot of disk space,
takes an age to link, and means you can't ship small patches.
I remember those days... linking a 50megabyte executable on a 25mhz
'040 Cube w/64MB of RAM took around 40 minutes. Loading/running in
GDB took another hour. It made one rather careful in the whole
Edit/Compile part of the Edit/Compile/Run loop.
b.bum
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.