commit | 6af7cbe855b4a047038e5e9b6e461af120bbfed8 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Aug 26 18:41:04 2020 -0700 |
committer | Colin Cross <ccross@android.com> | Tue Sep 01 01:26:50 2020 +0000 |
tree | ff9838827bd015cccb31e43a334076a8f423d156 | |
parent | a6de2ada157fbd990345e6f0e62854768deedc77 [diff] |
Fix BOARD_PREBUILT_(VENDOR|ODM)_DLKMIMAGE support in target-files.zip BOARD_PREBUILT_ODM_DLKMIMAGE support seems to have been forgotten in target-files.zip, and BOARD_PREBUILT_ODM_DLKMIMAGE support had a typeo. Test: treehugger Change-Id: I9663220b43f0df4f39a7ef432ad4cfec39803a20
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.