| commit | c47b4ee74b11332a7597c259aa9d7712fe311859 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Thu May 14 16:40:12 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Thu May 14 16:46:26 2020 +0900 |
| tree | 0cb5927c45a2a5581a2d3b49a8d320d16c1d43eb | |
| parent | 09153e244e8e1681b5083c102dec47934c19583d [diff] |
Remove /default.prop It was kept for non-Treble devices, but now /system/build.prop is used instead by having both system-configured sysprops and vendor-configured sysprops. To summarize: * For Treble compliant devices - /system/build.prop has ADDITIONAL_DEFAULT_PROPERTIES PRODUCT_SYSTEM_DEFAULT_PROPERTIES props generated from buildinfo_common.sh props generated from buildinfo.sh props read from TARGET_SYSTEM_PROP file ADDITIONAL_BUILD_PROPERTIES - /vendor/build.prop has PRODUCT_DEFAULT_PROPERTY_OVERRIDES props generated from buildinfo_common.sh props read from TARGET_VENDOR_PROP PRODUCT_PROPERTY_OVERRIDES * For non-Treble devices, PRODUCT_DEFAULT_PROPERTY_OVERRIDES moves from /vendor/build.prop to /system/build.prop (just after PRODUCT_SYSTEM_DEFAULT_PROPERTIES). Other props in /vendor/build.prop remain there but they are not used because it's a symlink for /system/vendor/build.prop and init does not follow symlink. Especially, PRODUCT_PROPERTY_OVERRIDES is ignored. Someone might think this as a bug, which actually is, but this change doesn't attempt to fix that, because 1) that's out of scope of this change, and 2) we will anyway merge PRODUCT_PROPERTY_OVERRIDES and PRODUCT_DEFAULT_PROPERTY_OVERRIDES into one. Bug: 117892318 Test: TH passes Change-Id: I867f3615ef8c06650ab2ee96642bac4f6d8ca820
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.