platform_build

History

Dan Willemsen 41bc424c32 Use explicitly sized types in zipalign/ziptime getLongLE would return a 64-bit number with the upper 32-bits set when decoding a 32-bit number with the top bit set. Per the zip file format, it was only expected to return a 32-bit number. Use explicitly sized types so that we use the proper sizes and don't do any implicit extensions. Change-Id: I5a4304dc99ce5f8f17284d4ca3094ae115207a1e		2015-11-04 23:52:52 +00:00
..
Android.mk	Add LOCAL_MODULE_HOST_OS	2015-09-03 16:40:51 -07:00
README.txt	Revert "Remove changing uids/timestamps from zip/jar files"	2015-10-29 21:26:18 +00:00
ZipAlign.cpp	Revert "Remove changing uids/timestamps from zip/jar files"	2015-10-29 21:26:18 +00:00
ZipEntry.cpp	Use explicitly sized types in zipalign/ziptime	2015-11-04 23:52:52 +00:00
ZipEntry.h	Use explicitly sized types in zipalign/ziptime	2015-11-04 23:52:52 +00:00
ZipFile.cpp	Use explicitly sized types in zipalign/ziptime	2015-11-04 23:52:52 +00:00
ZipFile.h	Use explicitly sized types in zipalign/ziptime	2015-11-04 23:52:52 +00:00

README.txt

zipalign -- zip archive alignment tool

usage: zipalign [-f] [-v] <align> infile.zip outfile.zip
       zipalign -c [-v] <align> infile.zip

  -c : check alignment only (does not modify file)
  -f : overwrite existing outfile.zip
  -p : page align stored shared object files
  -v : verbose output
  <align> is in bytes, e.g. "4" provides 32-bit alignment
  infile.zip is an existing Zip archive
  outfile.zip will be created


The purpose of zipalign is to ensure that all uncompressed data starts
with a particular alignment relative to the start of the file.  This
allows those portions to be accessed directly with mmap() even if they
contain binary data with alignment restrictions.

Some data needs to be word-aligned for easy access, others might benefit
from being page-aligned.  The adjustment is made by altering the size of
the "extra" field in the zip Local File Header sections.  Existing data
in the "extra" fields may be altered by this process.

Compressed data isn't very useful until it's uncompressed, so there's no
need to adjust its alignment.

Alterations to the archive, such as renaming or deleting entries, will
potentially disrupt the alignment of the modified entry and all later
entries.  Files added to an "aligned" archive will not be aligned.

By default, zipalign will not overwrite an existing output file.  With the
"-f" flag, an existing file will be overwritten.

You can use the "-c" flag to test whether a zip archive is properly aligned.

The "-p" flag aligns any file with a ".so" extension, and which is stored
uncompressed in the zip archive, to a 4096-byte page boundary.  This
facilitates directly loading shared libraries from inside a zip archive.