commit | 7a0e042276dcbe2cb28e340e5e4ec8c98ab62b4a | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Thu Jan 04 22:01:30 2024 +0900 |
committer | Jiyong Park <jiyong@google.com> | Thu Jan 04 23:48:27 2024 +0900 |
tree | 06f1dd1097fd76c3474ac8ed0852aa274bfc9393 | |
parent | 0284ba297c6923bea03aa346b52fc02642230a1b [diff] |
Add BUILD_BROKEN_DONT_CHECK_SYSTEMSDK https://android-review.git.corp.google.com/q/topic:limit_systemsdk introduced a new check for preventing the use of system SDKs above 34 from Java modules in the vendor partition. As this may break some unprepared targets, introduce BUILD_BROKEN_DONT_CHECK_SYSTEMSDK as a temporary escape hatch. This flag will be deleted eventually. Bug: 314011075 Test: Add BUILD_BROKEN_DONT_CHECK_SYSTEMSDK := true to BoardConfig.mk Change-Id: Ie70ce428ec3df8580099efd99e5c7c9c4f9daecb
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.