| commit | df09892cdb10dd5af52ca6af51178c4519077672 | [log] [tgz] |
|---|---|---|
| author | SzuWei Lin <szuweilin@google.com> | Tue Jun 25 17:49:01 2019 +0800 |
| committer | SzuWei Lin <szuweilin@google.com> | Tue Jul 09 18:13:22 2019 +0800 |
| tree | e1ffae2f7504ac316c8d446266da04cc5446b1b4 | |
| parent | 9392fb3905991555d42812934e3755ef77bb65e2 [diff] |
Revise GSI targets to inherit from mainline_system directly The patch seperates gsi_common.mk to aosp_product.mk and gsi_release.mk. Let GSI targets can be inherit with 3 parts: - system: mainline_system.mk - product: aosp_product.mk - vendor: none or emulator vendor makefiles aosp_product.mk includes the AOSP packages/settings will be in the product partition. GSI targets also includes the gsi_release.mk, which contains the special settings for the GSI for releasing, ex. skip_mount.cfg, extra VNDK, etc. After the patch, the build targets inherit from aosp_$arch.mk will not apply these special settings anymore. The gsi_common.mk, legacy_gsi_common.mk and aosp_$arch_ab.mk will be phased out later. Bug: 135502030 Test: build gsi_arm64-userdebug and aosp_arm64-userdebug, compare Test: root, system and vendor in out folder with/without the patch Change-Id: Ic604ac91ba9a704e6507bac324d19bbf68063464
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.