| commit | 37a037e05eebb7e10d2a4c6517146bbe188cb0f3 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Dec 16 11:06:30 2019 +0000 |
| committer | Anton Hansson <hansson@google.com> | Mon Dec 16 11:27:18 2019 +0000 |
| tree | 81c5364abebd1054ed37e2a7dbe60b62940f07f2 | |
| parent | 8e3bc2d4cedd205c8e2f845bf2619dfb8b14443f [diff] |
Verify updatable jars are in PRODUCT_BOOT_JARS A jar should never be in just the updatable list. Test: treehugger Change-Id: I806eb2d00502f98aa2c40fba3fc644cfddc64ad9
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.