A few LOCAL_ADDITIONAL_DEPENDENCIES were required, where
LOCAL_REQUIRED_MODULES would be nicer, but you can't require a module of
the same name. It would create a dependency loop with the current
require implementation, so it's filtered by the build system.
Also translate monkey from ALL_PREBUILTS to a prebuilt like the rest of
the tools. This doesn't change anything, since 'monkey' is already in
build/target/product/base.mk.
ACP is being removed, so use the standard build system macros to copy
files.
Change-Id: I4f73c6b35c0d7ae25467145b0a9d5c32ba4578d2
Hasn't been touched since cupcake, and only builds if you're targeting 32-bit
ARM, which no target still does anyway.
Change-Id: I6860a34c72c21ca7e04df288631a8950732b2e97
The previous code used unzip to get the offsets of the files in
the zip file. This was an estimate, and it turns out to be wrong
in many cases. Replace that with zipinfo -v which gives the exact
offset of the files in the zip.
Also update the tmp files so that they are in a dictionary of their
own by apk, instead of embedded in the offset list.
Change-Id: I8f5efd95f2d2e39e20cc0b6b6571b799be21ef32
The CallStack function prints stacks to the log. Unfortunately, our
stack script defaults to arm, so if the data is actually arm64, we'll
do nothing. Modify the script to parse the input trying to determine
the abi before processing the rest of the lines. At the very least,
we'll be able to correctly choose between arm and arm64.
The only downside, is that, the old method could take dumps from different
abis, but no one I know does this.
Bug: 26569638
Change-Id: I5935b82fe0af1e788b0d3edc535b9f0cbb7d1b28
Not sure exactly why this happens, but it keeps cropping up on my JB
nakasi when running the NDK tests.
Change-Id: Ic5c35f9ab01c0a83f98a6d074220c89ec765a812
Required if it is to deal with v52 class files.
Bug: 27189914
(cherry-picked from commit 79c3a724b8)
Change-Id: I8647dd7807a153457e5af5ff13a414af853057ab
This is to move OTA update package verification logic for new Android
devices from SHA-1 to SHA-256.
Prior to this change the script which generates new signing keys
used SHA-1 in certificates. This change switches the script from SHA-1
to SHA-256. The reason is that OTA updates are accepted only if they
are signed using the same digest algorithm as in the certificate.
Bug: 25643280
Bug: 20580998
Change-Id: I9babe85946a43697aeb4309837504aea25e26763
The new API generator uses ASM 5.0.4 instead of 4.0, which makes
it capable of handling class files format 52. It also drops the
dependency on the SDK common jar and only depends on Guava (and
ASM), using the offline Maven repository directly.
(cherry-picked from commit 1d7a69a635)
Change-Id: Ia8322366f4a8f7a70610d07104375f53d54aab01
