summaryrefslogtreecommitdiff
path: root/libs/androidfw/AssetManager2.cpp
diff options
context:
space:
mode:
author Yurii Zubrytskyi <zyy@google.com> 2024-06-06 15:20:41 -0700
committer Yurii Zubrytskyi <zyy@google.com> 2024-06-12 21:57:04 +0000
commit9ab48e85f1174249e6f6bdc809b4101ffadcf117 (patch)
tree67425140808448c38208342e1d71a1d66db7d8a4 /libs/androidfw/AssetManager2.cpp
parent9687d080317c683853c4b80ce703597426a1b67c (diff)
[res] Correct, optimize adding shared lib assets
When we add shared library assets to all ResourceImpl objects there are several important details: 1. ApkAssets array contains both file-based and loader-based assets, and they have to be partitioned in this order, otherwise loaders won't be able to overlay all file assets 2. When adding all shared library assets they also may contain frros, and those need to be loaded as overlays explicitly 3. No need to repeatedly add each asset path as it involves the same steps of checking for duplicates and rebuilding the native structures 4. Given it's the constructor and it will force-set the configuration later, adding assets can be done in 'preset' mode without calculating anything config-related. Bug: 345562237 Test: build, atest ResourcesManagerTest, simpleperf FRRO changes Change-Id: Ia000549bbec06d5b8f649c7bff636c4f2a1dac22
Diffstat (limited to 'libs/androidfw/AssetManager2.cpp')
0 files changed, 0 insertions, 0 deletions