diff options
author | 2025-02-27 07:44:51 +0000 | |
---|---|---|
committer | 2025-02-27 09:25:34 +0000 | |
commit | 853a7a471a2c70f03a934161f264fe69240f829c (patch) | |
tree | 2695b0eaaa0640838b0bdf3da8d4107f50b15a72 /scripts/aconfig-to-metalava-flags.py | |
parent | 54af357e04d41873a0a13a8ca14988099e9aa6d5 (diff) |
Generate META/(root|vendor_boot)_filesystem_config.txt
Unlike other partitions like system, vendor, ..., the build rule for
this will be created in android_device, and will use the intermediates
directories assembled by android_device for target_files.zip creation.
The alternative would be to create this files in filesystem's
GenerateAndroidBuildActions, but it would require handling the following
- root_filesystem_config.txt: This can be created in system's
GenerateAndroidBuildActions, but we would need to assemble a separate
"root" staging dir without "system" subdir
- vendor_boot_filesystem_config.txt: This can be created in
vendor_ramdisk's GenerateAndroidBuildActions, but we would need to
copy the recovery files to the staging dir before running fs_config
Test: Verfied that vendor_boot_filesystem_config.txt is identical
Test: root_filesystem_config.txt has the following diffs
```
32d31
< odm_dlkm/etc 0 0 644 capabilities=0x0
47d45
< vendor_dlkm/etc 0 0 644 capabilities=0x0
```
This is due to a preexisting diff in Soong's target_files/ROOT
intermediates. I will debug this in followup work
Bug: 388633394
Change-Id: Ia21f1456cbc1a1641db1c01416cdc575600770cf
Diffstat (limited to 'scripts/aconfig-to-metalava-flags.py')
0 files changed, 0 insertions, 0 deletions