Previously the base APK would be considered without
any splits loaded into the same AssetManager. This would
prevent splits from overriding attributes in the
AndroidManifest.xml, such as enabled state based on
version, etc.
This CL loads all APKs in the cluster into a common AssetManager
from which the base AndroidManifest.xml is parsed.
Bug:17006358
Change-Id: Ib88096c49d0c4f743b7e6ba0921251459bee107c
Caveat: There are two bugs:
- Mipmap definitions get placed in all splits.
- mdpi drawable doesn't get split properly.
Change-Id: I53b8e54cbcb3dfba495ec68e602f98666e8883a7
Build multiple APKs, each containing a disjoint subset
of configurations. These can then be loaded into the device
AssetManager and should operate as if they were never split.
Use the idea of building multiple sets of files, where each
set represents an APK. An ApkBuilder can place files
in a set based on its configuration, but you can actually
add directly to a set, in the case of the resources.arsc and
generated AndroidManifest.xml for splits.
Change-Id: Ic65d3f0ac1bbd290185695b9971d425c85ab1de3
