| commit | 2c807515c08e4f25e46140c6f7718e338b47d8ba | [log] [tgz] |
|---|---|---|
| author | Mark White <anothermark@google.com> | Wed Oct 25 17:27:07 2023 +0000 |
| committer | Mark White <anothermark@google.com> | Wed Oct 25 17:34:04 2023 +0000 |
| tree | 6e0836a87929ecc81dce80e9222a6c9c406e5ca4 | |
| parent | ea9d5cfbeb0cbf0d4bfc9d368983e0ae9b25d2d1 [diff] |
Suggest developers use -eng builds instead when they lunch -userdebug This is because -eng provides faster local builds. (also moving hints to where they are more likely to be seen) Test: lunch cf_x86_64_phone-userdebug Fixes: 307753064 Change-Id: I52cf9e9c399dbb3a52c7952f7204a9e567d15c22
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.