| commit | c6446515171c503800485cf41a065ad97bc69f46 | [log] [tgz] |
|---|---|---|
| author | Calin Juravle <calin@google.com> | Thu Apr 26 18:52:45 2018 -0700 |
| committer | Calin Juravle <calin@google.com> | Mon Apr 30 12:14:09 2018 -0700 |
| tree | 2df18d15ae1cd1797cb38d052c37fd435dd51379 | |
| parent | 62c28938496de080ba3c3f4f4ce41ef1f44c9a10 [diff] |
Pass --dex-location when processing prebuilt profiles
The apk name does not match the install location at the stage we are
processing profiles. This causes the wrong profile key to be used in the
final profile which may generate an empty app image.
Test: m; flash, dumpsys dexopt and check for speed-profile
check that the app image is not empty
Bug: 78515726
(cherry picked from commit 60216615f4d03defc38a12c9417175319e08870a)
Merged-In: Ic5d71296583be71d96f0e7a2dd59753f1d23c350
Change-Id: Ieb7386701b631d53d452336d1ad22653e4daee42
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.