site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Fri, Aug 28, 2009 at 00:03, Joel Reymont<joelr1@gmail.com> wrote:
Unfortunately, @executable_path in Firefox dylibs seems to prevent them from getting into the cache, something I plan to fix using install_name_tool.
Surely that’ll then prevent drag-and-drop installation of Firefox, moving it even further _away_ from your average Mac app? It strikes me that, from what you’ve posted here, the dyld issue as compared to Safari is that: - Firefox loads lots of dylibs - Those dylibs are specific to Firefox (and bundled with it) - Safari loads lots of dylibs - Those dylibs are used by lots of other things and part of shared frameworks It makes perfect sense that Safari’s frameworks would be cached while Firefox’s wouldn't, because nearly everything that Safari uses is used by other apps too; this doesn't apply to Firefox. Attempting to get Firefox’s (private) dylibs added to the shared dylib cache would surely be an abuse of mechanism. I dread to think what would happen if lots of app developers thought _their_ apps were important enough to warrant it. I can’t think of another way of putting this, but aren’t you trying to get all the advantages of apps built predominantly using hot, shared, dylibs in an app which eschews much of that to do its own thing? (I'm almost curious enough to go and find out what the playing field is for Camino in this respect, given it's more “native” than FF). By all means, make Firefox faster on the Mac—there are lots of people who prefer it over Safari, after all—but I can’t help but wonder if you might be fighting a losing battle in some avenues. M. -- http://nevali.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com