| commit | 301c6f471bb5ce7b63a7773c1e6709b93e7b1db8 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Apr 01 21:24:12 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Thu Jul 18 15:46:31 2019 -0700 |
| tree | 30b4c0b95c920b2ccbeb06cf53ab629530f1fa17 | |
| parent | 25cf50f582e680daf82b83f4bb541481d31ffe72 [diff] |
Removed an obsolete TODO. The intended check was to ensure system image won't be built as a chained partition when using dynamic partitions. Because such an image can't be verified by bootloader. As it evolves, GSI system image has been built against the intended check. Because GSI system image will be verified by first stage init in userspace. Bug: 80195851 Test: TreeHugger Change-Id: I45b079799e5d7443e82d73d43e2b63c613f33165
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.