| commit | b607281fae5aeaaf8848d01a60c4b7ec4d04c2c4 | [log] [tgz] |
|---|---|---|
| author | Liz Kammer <eakammer@google.com> | Fri Jun 23 11:22:42 2023 -0400 |
| committer | Liz Kammer <eakammer@google.com> | Fri Jul 21 15:51:58 2023 -0400 |
| tree | 3e69b179e9062efbe0bf897d559b409e7e265448 | |
| parent | 0ee11559f94034b559d9d53f6c8da1467d9272fe [diff] |
Allow setting some build_broken out of boardconfig Some build broken flags are for cross-cutting features rather than board-specific. In order to support these without requiring broad changes across many board configs, these can be set in a buildspec.mk files. Test: set build_broken flags in environment, get expected fail Test: set build_broken flags in buildspec, get expected success Change-Id: I8a74c30575f6bf40e46281ca5f37f3cfed526ec5
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.