зеркало из https://github.com/mozilla/gecko-dev.git
baba0e3cec
The jar log is used for optimization of the packaged jar files according to their usage patterns during a profile run. The current content of the file currently come with 2 caveats: - it contains entries for jar archives that aren't relevant to packaging, which is not a problem in itself, but see below. - it contains full paths for jar archives that may not correspond to the location of the packaged directory (on e.g. Android, where the build almost certainly doesn't happen in the same directory on the host as Fennec runs in the emulator/on the device). The current JarLog code does somehow handle the various ways paths are currently presented, but it's clearly missing code to map the paths in the log to packaged paths. Instead of requiring manual work and extra build options to handle this mapping, and considering the caveats above, it's just simpler to log archive paths as if they were relative to the packaged application directory in a build, and use that during packaging. Depends on D21655 Differential Revision: https://phabricator.services.mozilla.com/D21656 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
test | ||
zipwriter | ||
appnote.txt | ||
components.conf | ||
moz.build | ||
nsIJARChannel.idl | ||
nsIJARURI.idl | ||
nsIZipReader.idl | ||
nsJAR.cpp | ||
nsJAR.h | ||
nsJARChannel.cpp | ||
nsJARChannel.h | ||
nsJARInputStream.cpp | ||
nsJARInputStream.h | ||
nsJARProtocolHandler.cpp | ||
nsJARProtocolHandler.h | ||
nsJARURI.cpp | ||
nsJARURI.h | ||
nsZipArchive.cpp | ||
nsZipArchive.h | ||
zipstruct.h |