| commit | f340066ee37e3c91fff5858474d4bbfe9abe89db | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Sat Apr 27 00:22:20 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Mon Apr 29 22:06:43 2024 +0000 |
| tree | 62596dc38a49c88aa0e4ffa4f09dcf1c704b8174 | |
| parent | 2bdaea7e20c0abaaf56c9f18afbe0bb02a89c02f [diff] |
Align boot jar exclusion with apex_contributions `RELEASE_APEX_BOOT_JARS_PREBUILT_EXCLUDED_LIST` exists to flag apex boot jars that may exist in source builds, but not in a google apex prebuilt (a prebuilt might not have been generated yet). This is a build flag, and exists in the <rel>.scl It is feasible that certain products in a specific release config never use apex prebuilts. Therefore, we need to selectively apply `RELEASE_APEX_BOOT_JARS_PREBUILT_EXCLUDED_LIST` to products that use apex prebuilts. At ToT, this is done via looking at module_build_from_source_value of ANDROID soong config namespace, and <apex>_module soong config namespace for every optional module. <apex>_module soong config namespace was removed in https://r.android.com/3056785. In preparation for removing module_build_from_source, use `PRODUCT_BUILD_IGNORE_APEX_CONTRIBUTION_CONTENTS` to determine if prebuilts are being used. Test: in internal, lunch barbet-ap2a-userdebug && get_build_var APEX_BOOT_JARS_EXCLUDED com.android.mediaprovider:framework-pdf com.android.mediaprovider:framework-pdf-v (this is the only release config where there is a delta between prebuilt and source apex boot jars) Test: in internal, lunch barbet-trunk_staging && get_build_var APEX_BOOT_JARS_EXCLUDED "" (empty string) Change-Id: I981ad3a7767f3602a844c8d53eadfd1f2e5db420
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.