| commit | b6eeae7289a1d7d0905c303d5bf5e9501e041189 | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Fri Oct 04 20:31:45 2019 +0100 |
| committer | Nikita Ioffe <ioffe@google.com> | Mon Oct 07 12:14:08 2019 +0100 |
| tree | 464aa0ae98c98d281db3d42f0742d68c50ad1460 | |
| parent | f89f29d669387d0376b0594b0ee1a1447cd09906 [diff] |
Unconditionally install shim apex on system partition Trying to do it on per-device basis is prone to errors and already bitten us several times. For example, currently aosp_taimen doesn't install shim apex on system partition, but specifies ro.apex.updatable = "true", which means that it doesn't pass CTS tests. Unconditionally installing shim APEX shouldn't introduce any problems since apexd will skip its activation of devices that don't support updatable APEX. Test: m checkbuild Bug: 140957666 Change-Id: I6b5e668b40b97752295c831684a7291842533c40
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.