LineageOS/android_packages_modules_common
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use module specific soong variable when last_optional_release is set.

Browse Source 
The original idea of using module specific soong variable was for the modules when they start off as optional module (before transition to mandatory). However, practically at build time, it can remain optional. For now, we will keep self.last_optional_release as the condition and the module can have their specific variable (for enabling/disabling prebuilts) by setting last_optional_release.

Bug: 301183608
Test: atest mainline_modules_sdks_test --host
      packages/modules/common/build/mainline_modules_sdks.sh
Change-Id: I8af5d3dd8733d244c2ade1d9b5118308b3c00622
This commit is contained in:
Alyssa Ketpreechasawat
2023-09-28 02:46:56 +00:00
parent bc25b72229
commit 25a6a5df1b
3 changed files with 140 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
build/mainline_modules_sdks.py
View File

@@ -922,8 +922,7 @@ class MainlineModule:
# If the module is optional then it needs its own Soong config
# variable to allow it to be managed separately from other modules.
if (self.last_optional_release and
self.last_optional_release > build_release):
if self.last_optional_release:
config_var = ConfigVar(
namespace=f"{self.short_name}_module",
name="source_build",