| commit | d4f9d626255a83edd7a13a8cf2513f5aca0bf394 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Apr 08 17:47:35 2019 +0100 |
| committer | Anton Hansson <hansson@google.com> | Tue Apr 09 16:28:22 2019 +0100 |
| tree | b553748416a5897d291fa180bc8f30a87046a246 | |
| parent | d31e4a9f8572e7ccfb719837d39b87b40fad93d0 [diff] |
Move bootimage props to vendor/build.prop Prior to this change the properties were in system/etc/default.prop. These properties are device-specific and don't really belong on the /system partition. I anticipate further change to these properties in the future: - pruning down the set of properties, as the .product. props don't make much sense for the boot image - moving them to the ramdisk instead Bug: 130025216 Test: boot into recovery, observe title (shows bootimage fingerprint) Change-Id: I9e92c1ec7068ae18fa0d709c77eac22a6b88c3d8 Merged-In: I9e92c1ec7068ae18fa0d709c77eac22a6b88c3d8
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.