commit | 012118da8f5f46eb34240b6a804c3a8a768d126e | [log] [tgz] |
---|---|---|
author | Po Hu <po.hu@mediatek.com> | Fri Mar 13 14:14:27 2020 +0800 |
committer | juju sung <juju.sung@mediatek.com> | Thu Mar 26 10:31:39 2020 +0000 |
tree | b173f2f46201c093b0e83a72cca7933c55665af4 | |
parent | 07c20355acc389316d8f1402266730cd9231d295 [diff] |
Add PRODUCT_BOOT_JARS_EXTRA interface This interface allows vendor to append their boot jars after AOSP's without changing inherit order. Test: get_build_var PRODUCT_BOOT_JARS Change-Id: I6beb8cc9d7fcf0d474b24f634e81657aa42e7ed7 Bug: 152267233
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.