finalize-module-sdks: apply hotfixes Code starts breaking because of only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type errors already after finalize-module-sdks, so move the hotfixes from finalize-platform-sdk to finalize-module-sdks. Also update the hotfix for CTS to include breakage previously missed. Also add hotfix for errorprone false positive [NewApi] in frameworks/opt/net/wifi. Bug: 481594013 Test: finalize-module-sdks && m out/soong/.intermediates/packages/modules/Permission/tests/cts/permissionui/UsePermissionApp30WithBluetooth/CtsUsePermissionApp30WithBluetooth/android_common/kotlin/CtsUsePermissionApp30WithBluetooth.jar out/soong/.intermediates/packages/apps/Settings/Settings-core/android_common/kotlin/Settings-core.jar out/soong/.intermediates/cts/tests/tests/appop/CtsAppOpsTestCases/android_common/kotlin/CtsAppOpsTestCases.jar Change-Id: Ib28f5bc29584fa3eb5bb6849ff8b1ae709a64d0d
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.