commit | b8cab053bde62b04048dc82a043be5063ef40290 | [log] [tgz] |
---|---|---|
author | Jihoon Kang <jihoonkang@google.com> | Thu Jan 09 22:58:05 2025 +0000 |
committer | Jihoon Kang <jihoonkang@google.com> | Thu Jan 09 15:33:55 2025 -0800 |
tree | 8db560380d6ac3cacbe41e5f8981ff1d4acd32fa | |
parent | ab314a9f15031d0c734d86b6f19e631df415cbc5 [diff] |
Export userdata partition related variables to Soong Were imported to Soong in https://r.android.com/3342023 but not exported from Make. Test: Verify that userdata.img is created in soong only build Change-Id: Ie5d9007a33ec89b9d1872d983684390d4ff21edf
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.