![]() ![]() ![]() Though since the switch to places-based bookmarks, it might have gotten better (the worst case being the loss of bookmarks, previously)įWIW: (since this got mentioned in #573958) ![]() I think it would be better if that wasn't necessary at all, and if firefox wasn't destroying profiles when it doesn't quite have the right to write it, but has enough rights to destroy it. > Do you think it makes sense to merge that into early app startup? Wouldn't be > echo "Could not find the correct home directory. Ld.so understands the string $ORIGIN (or equivalently $ | cut -f6 -d:` (We would still need a wrapper script for running out of the build tree, but that's not the case we care about for performance, and that script could be much simpler.) The SONAMEs we assigned would presumably involve the Gecko version - it seems to me that we do make pretty strong binary compatibility guarantees within one Gecko version.Ģ) If we decide we want to go for static linkage of most of those libraries into the 'firefox' binary anyway ( bug 525013) we could make firefox-on-top-of-xulrunner the normal release build configuration (I don't know how this works but I know several Linux distributions do it), put xulrunner in /usr/bin, and only worry about binary compatibility for the libraries that are still dynamic (presumably just libxpcom.so at that point, plus system stuff?)ģ) If (1) and (2) are not feasible we could look into expanded use of $ORIGIN, which used to be a Solaris-ism but I believe is now quite widely available. as just plain 'firefox' etc., and throw the wrapper scripts away in an installed configuration. The purpose of the wrapper scripts is to tell the dynamic linker where our private libraries live, so here are three possible ways to get rid of them:ġ) If all the shared libraries installed by an -enable-libxul build have sufficiently stable public ABIs, we could give them SONAMEs, install them in /usr/lib, install firefox-bin etc. ![]() Bug 550310 observes that the 'firefox' and 'run-mozilla.sh' wrapper scripts add significant startup overhead on systems where they are used (Unix that is not OSX, if I understand correctly). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |