History log of /frameworks/base/tools/aapt/ApkBuilder.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6240840387335632fdc92d5d168f924e2f414dda 08-Aug-2014 Adam Lesinski <adamlesinski@google.com> Ensure that split names are valid

Generate valid split names for resource splits.
Validate split names for features.

Change-Id: I3040438af0156778c2bd66ddeffdf62fe9dcc9fc
/frameworks/base/tools/aapt/ApkBuilder.h
3921e87e6e67a063caa1987937d7944b24aef489 13-May-2014 Adam Lesinski <adamlesinski@google.com> Quick fix to ensure mipmap doesn't get stripped by AAPT

This is a quick fix. A refactoring is already underway to properly
solve this problem.

Bug:14857725
Change-Id: Ic0c475aa0b180803a687904ad9f71eb87e137a25
/frameworks/base/tools/aapt/ApkBuilder.h
fab50875b98e8274ac8ee44b38ba42521bbbf1f9 16-Apr-2014 Adam Lesinski <adamlesinski@google.com> Add support for building split APKs

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
/frameworks/base/tools/aapt/ApkBuilder.h