platform_build

History

Tianjie 2751d2b8f3 Change the parameter type of offset in read As we support zip64 in libziparchive, we change the parameter of the ReadAtOffset() in zip reader from uin32_t to off64_t. So the derived class needs to be updated as well. Bug: 150900468 Test: build Change-Id: Icbfd2dd54b01ff62da988ba8598c1057f9bb6368		2020-04-02 06:16:43 +00:00
..
Android.bp	zipalign: Fix build failure in static_sdk_tools.	2017-11-06 11:12:08 -08:00
README.txt	Revert "Remove changing uids/timestamps from zip/jar files"	2015-10-29 21:26:18 +00:00
ZipAlign.cpp	Move zipalign off NO_ERROR.	2018-10-08 11:19:28 -07:00
ZipEntry.cpp	Move zipalign off NO_ERROR.	2018-10-08 11:19:28 -07:00
ZipEntry.h	Fix or suppress some google-runtime-int warnings.	2018-08-10 15:14:26 -07:00
ZipFile.cpp	Change the parameter type of offset in read	2020-04-02 06:16:43 +00:00
ZipFile.h	Fix or suppress some google-runtime-int warnings.	2018-08-10 15:14:26 -07: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.