| commit | 4b1deb8c7a052c79f8cde7ba90b1ca54c4b11cef | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Tue Oct 22 23:22:51 2024 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Tue Oct 22 23:22:51 2024 +0000 |
| tree | fdd59a43af6a83d50c333654347d197bd17e250c | |
| parent | bc5d94562fe5a305e30017f6e9f5ea86013cdd94 [diff] |
Export BUILDING_PRODUCT_IMAGE to Soong The variable is used to determine whether a product partition filesystem module is generated for a specific product Test: m soong_generated_product_filesystem_test Bug: 374388294 Change-Id: I2994a6031572427f016d258ad7961a2c29faf0e8
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.