commit | 8a1a1858ce8f1e20dd2588c4b71b0eaca703435d | [log] [tgz] |
---|---|---|
author | Inseob Kim <inseob@google.com> | Sun Feb 09 20:17:15 2025 -0800 |
committer | Inseob Kim <inseob@google.com> | Mon Feb 10 13:22:48 2025 +0900 |
tree | e7d6b6dff5fef1c698a2e76bd067c87a2d18e134 | |
parent | e3dee679310af4c568d3ccedc3948cde639e3dbc [diff] |
Add soong module only for aosp_{arch} aosp_{arch} build GSIs for release, whereas gsi_{arch} build GSIs for compilance test. System images of aosp_{arch} are supersets of system images of gsi_{arch}, with a few exceptions (userdebug sepolicy). This adds a Soong module for aosp_{arch} targets, named aosp_system_image, enabled only when building GSI. This change is a reland of ag/31654647 where the build is broken on targets of downstream branches which inherit aosp_{arch} targets. Bug: 381019944 Test: build, TH Change-Id: I390d59cb4168eee8c422a4c1b257ade465d17921
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.