| commit | a784ef197c6ba7d33aa17c6812c953f78fab7c62 | [log] [tgz] |
|---|---|---|
| author | Chris Gross <chrisgross@google.com> | Mon Apr 22 11:09:57 2019 -0700 |
| committer | Chris Gross <chrisgross@google.com> | Tue May 07 11:00:37 2019 -0700 |
| tree | 279b8f3c249b14e039c81a6834a69015694688be | |
| parent | 7dbbc3075b5f4f3bc91eeecf3d7e3df429c60e5b [diff] |
Add BUILD_RECOVERY_IMAGE and BUILD_BOOT_IMAGE flags Bug: 123428770 Test: Built system-only image and checked that no boot.img or recovery.img files where created. Booted the resulting merged build on device. Change-Id: I760476502775e68125907c39e66b8665e789a798
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.