d8c4c30ba4
When BOARD_SYSTEMSDK_VERSIONS is set, any apk in the vendor partition is force built against SystemSDK (or Android SDK if LOCAL_SDK_VERSION is set to current). However, there should be one exception to this: RRO for framework-res.apk. This is because the RRO is currently overriding resources that are not part of SystemSDK. Until SystemSDK is expanded to cover resources that are eligible for overriding, let's allow the direct dependency from RRO to framework-res.apk. Bug: 35859726 Bug: 76398918 Test: m -j for 2018 Pixels Change-Id: Ib9981b107d78691eef21f4525ebdac9866d5c50e |
||
|---|---|---|
| core | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.mk | ||
| Changes.md | ||
| CleanSpec.mk | ||
| OWNERS | ||
| README.md | ||
| Usage.txt | ||
| buildspec.mk.default | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| tapasHelp.sh | ||
README.md
Android Make Build System
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.