| commit | c426b3f0b6094632b76da4e26aaa162e64e2782d | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Fri Feb 08 14:03:40 2019 -0800 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Feb 08 14:03:40 2019 -0800 |
| tree | 58ad6c2d303372581abc1c515b94bd7106bd9368 | |
| parent | 300662ed404f8278f9c72e4364521d057b473d25 [diff] | |
| parent | 00d80348f264e39f26884f4933cca4f7b9e82189 [diff] |
[automerger skipped] Merge "Default to erroring when eng/debug tags are used" am: 7067aaa13c am: 265bd2fb92 am: 00d80348f2 -s ours am skip reason: change_id I1534a0db006d72c7921a20ab793586ef1c7bdb21 with SHA1 5dbf6e052a is in history Change-Id: I5e0be44245d8e73385fbb4875c23abee6a3d0476
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.