commit | 67932ab694e636c48b332d702982c649cd969338 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Fri Apr 19 00:09:16 2019 -0700 |
committer | Tao Bao <tbao@google.com> | Mon Apr 22 21:08:25 2019 -0700 |
tree | 3958d67e586818a1f9741b7bc62487a41a44672a | |
parent | 22c434e80f89d348d6c99be3c6836f8ed26e2ce3 [diff] |
Write ro.build.ab_update to /vendor/build.prop. It's a vendor-specific property, which was historically included into /system/build.prop prior to this change. Whether a target uses A/B OTA shouldn't affect anything on the system image, including the `ro.build_ab_update` property. Moving it to vendor partition will also make it consistent with other A/B specific configs, such as the `slotselect` flag in device fstab (/vendor/etc/fstab.$(PRODUCT_PLATFORM)). Bug: 130516531 Test: Build and flash crosshatch-userdebug. Check /system/build.prop, /vendor/build.prop and the runtime property. Change-Id: I927625fbcc02c4a875a1f39850b51576f5ff6c66
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.