diff options
| author | Dan Willemsen <dwillemsen@google.com> | 2017-02-17 13:14:43 -0800 |
|---|---|---|
| committer | Dan Willemsen <dwillemsen@google.com> | 2017-02-17 13:21:03 -0800 |
| commit | a1354b325dec7379d4a5a10c8dceffe56339af68 (patch) | |
| tree | d31e6bf4accf04b85a9b7baaab61f92524b238a5 /androidmk | |
| parent | 449887957cab752f993b55cc5ffe72afed9a4420 (diff) | |
| download | build_soong-a1354b325dec7379d4a5a10c8dceffe56339af68.tar.gz build_soong-a1354b325dec7379d4a5a10c8dceffe56339af68.tar.bz2 build_soong-a1354b325dec7379d4a5a10c8dceffe56339af68.zip | |
Fix Zip64 behavior in zip2zip
This was blindly copying the zip64 extra fields from the central
directory of the original zip file to the new one. The zip64 extra
fields depend on the contents of the header it's attached toa, and in
this case we were copying the zip64 file header offset from the central
directory entry into the destination local file header, which makes no
sense, especially since the offset changed in the new file.
So strip all zip64 extra entries, and we'll create them as necessary
when writing ou the new file.
Bug: 34704111
Test: zip2zip on the original target-files -> img that was broken
Test: m -j blueprint_tools (new android_test.go)
Change-Id: Ie3c0540b13d3afcf42f3d47fff319065952b126f
Diffstat (limited to 'androidmk')
0 files changed, 0 insertions, 0 deletions