| 0e25d9ae776053d9186200f2f698faea45313cb6 |
|
11-Mar-2017 |
Adam Lesinski <adamlesinski@google.com> |
libandroidfw: Search all packages for an identifier
In order to allow multiple packages with the same package name, but
different package ID, we need to keep searching packages until the
resource is found.
Bug: 30999713
Test: make libandroidfw_tests
Change-Id: If4540e12731ca18a18e9e550a9bf248606a586c5
/frameworks/base/libs/androidfw/tests/data/feature/res/values/values.xml
|
| 351471f928022fb22a1b19f9e5e647a7901152fd |
|
12-Dec-2016 |
Adam Lesinski <adamlesinski@google.com> |
libandroidfw: Make tests less flaky
Changing any of the test APKs could change resource IDs.
The resource IDs are all made public and assigned an ID
to avoid this issue.
Test: make libandroidfw_tests
Change-Id: Idd17c25f4ac86a0ad5b2b8da6f968e5d9b2346c1
/frameworks/base/libs/androidfw/tests/data/feature/res/values/values.xml
|
| 60293197379e522c870c4a28462804207bab505d |
|
22-Oct-2014 |
Adam Lesinski <adamlesinski@google.com> |
Added some more Split density tests
Change-Id: I3b83515f1240e713bbcff5385cf054bba693f297
/frameworks/base/libs/androidfw/tests/data/feature/res/values/values.xml
|
| 833f3ccbc8f4dd1ec8abb9121988b99ff34ec4c1 |
|
19-Jun-2014 |
Adam Lesinski <adamlesinski@google.com> |
AAPT support for feature splits
This change allows the developer to add a base package for
which to build a feature split. The generated resource types
will begin after the base APK's defined types so as not
to collide or override resources.
Multiple features can be generated by first choosing an
arbitrary order for the features. Then for each feature,
the base APK and any preceding features are specified
with the --feature-of flags.
So with a base APK 'A' and features, 'B', and 'C',
'B' would be built with
aapt package [...] --feature-of A [...]
and 'C' would be built with
aapt package [...] --feature-of A --feature-of B [...]
Change-Id: I1be66e3f8df9a737b21c71f8a93685376c7e6780
/frameworks/base/libs/androidfw/tests/data/feature/res/values/values.xml
|