96949d3904
These properties, namely: - PRODUCT_SYSTEM_NAME - PRODUCT_SYSTEM_BRAND - PRODUCT_SYSTEM_MANUFACTURER - PRODUCT_SYSTEM_MODEL - PRODUCT_SYSTEM_DEVICE propagate into /system/build.prop as ro.product.system.* and can identify if the /system partition is mainline_system. These don't modify other ro.product.* properties that are defined in partitions other than /system. Bug: 110206836 Bug: 146191296 Test: lunch mainline_system_arm64-userdebug; m Test: lunch aosp_arm64-userdebug; m Test: Two products must have same PRODUCT_SYSTEM_* props Change-Id: I300579d555d269481635237fb02aab5db71a510d |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
OWNERS | ||
README.md | ||
tapasHelp.sh | ||
Usage.txt |
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.