commit | 8a27a2b71e524884249bb750588f8a5df369e572 | [log] [tgz] |
---|---|---|
author | Nelson Li <nelsonli@google.com> | Thu Dec 05 06:26:09 2024 +0000 |
committer | Nelson Li <nelsonli@google.com> | Thu Dec 05 08:25:36 2024 +0000 |
tree | d873827313b76425748d5354606afd4cacca0d51 | |
parent | 1a309e58f267955e7f726bd276c19d4eff2093ab [diff] |
Ensure SOONG_CONV_DATA is generated even no modules require conversion This change ensures that the `SOONG_CONV_DATA` file is always generated, even when there are no modules that require conversion from Make to Soong. Previously, if no Android.mk files were present in the source code, the `SOONG_CONV` variable would be empty, preventing the creation of `SOONG_CONV_DATA` and causing build failures. Bug: 382385324 Test: m $ANDROID_PRODUCT_OUT/obj/PACKAGING/soong_conversion_intermediates/soong_conv_data Change-Id: Ifd9ec50e1615765f0d440a767a35f87d31a251f0
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.