commit | 06533fef4ae77758ae94464040b8a1d49d53349c | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Mon Sep 02 18:17:02 2019 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Tue Sep 10 21:55:32 2019 +0800 |
tree | 0e06a1628eaf007f232d4a618d7e9af258a4fe89 | |
parent | 5242dc18bfd13164dcbb02280153d72af9508168 [diff] |
Moving GSI-specific properties to /system_ext We're now adding a core CSI system.img that is common across different targets. So GSI-specific things should be moved to /system_ext. Also renaming various generic*/system.prop to generic*/system_ext.prop. This is to put the customization into /system_ext/build.prop instead of /system/build.prop. Bug: 137711197 Test: boot a GSI on crosshatch, and checks the value of those properties Change-Id: Id344124280d5f4a6c10d390a9e8a4a50cc7f28fb
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.