| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
libs/androidfw/ResourceTypes.cpp
tools/aapt/Android.mk
tools/aapt/StringPool.cpp
tools/aapt/StringPool.h
Change-Id: I9d69efdfb892032895ace12159d193304f02dc6c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- char16_t is a distinct type, so stay consistent
with it throughout the code base.
- char16_t is defined as minimum size of 16 bits.
Since we mmap and cast data structures onto raw memory,
we need a precise definition (uint16_t), so we cast between
that (and static_assert that they are the same size).
Change-Id: I869c32637543bbcfb39d2643e7d9df10d33acd3c
|
| |
| |
| |
| | |
This reverts commit 9f6a119c8aa276432ece4fe2118bd8a3c9b1067e.
|
| |
| |
| |
| | |
Change-Id: I3ffafdab27cc4aca256c3a5806b630795b75d5c8
|
| |
| |
| |
| |
| |
| |
| | |
The HAVE_(BSD|GNU)_QSORT_R in AndroidConfig.h has never worked, and we
should just be using something standard anyway.
Change-Id: I784d6212f6c890a11c4af2f83d1ce2d279708652
|
|/
|
|
|
|
|
| |
When compiling in C++ mode, the compiler will complain about conversions
from uint16_t to char16_t. Be consistent in using char16_t for strings.
Change-Id: I052b6176ced635162920b31560052d9a64f92764
|
|
|
|
| |
Change-Id: I11ee943da23a66828455a9770fc3c5ceb4bbcaa9
|
|
|
|
| |
Change-Id: Ic7c796e048cfe98ee355c18b3708fee5ea716e2e
|
|
|
|
| |
Change-Id: Ie79f81625947f4e95122047605d994c86e872e74
|
|
|
|
| |
Change-Id: I8bbec237229b05f96c708d41f3c4da17e2a90e2b
|
|
|
|
|
|
|
|
|
|
|
| |
The current implementation of Vector::sort uses insertion sort
on the assumption that the data is mostly sorted. It isn't.
This change brings the total time spent sorting packages by config
down to 500ms from about 93 seconds.
Bug: 6186278
Change-Id: Iec8da11e09297acd6c73733d063b0fa9dacf69f7
|
|
|
|
|
|
|
| |
The sorted string pool option was no longer used.
Neither were strings with associated identifiers.
Change-Id: Ic5f6368637fbeedfda873d63f4ad0f3ea9d0d603
|
|
|
|
| |
Change-Id: If93957a840a0f1cae2e6ef291eeeb1b0c7c20958
|
|
|
|
|
|
| |
step 2: move libutils headers to their new home: androidfw
Change-Id: I14624ba23db92a81f2cb929f104386e1fab293ef
|
|
|
|
|
|
|
|
|
|
|
| |
In our current environment with very many translations, this can
save a lot of RAM -- for example over 200K in Gmail just by sorting
the strings in the Gmail .apk (not the framework).
Also add a new aapt command to print the contents of the resource
table string pool.
Change-Id: I1da037b3e2c377b890833ff57ab158965314ac48
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allows the use of UTF-8 for packing resources instead of the
default of UTF-16 for Java. When strings are extracted from the
ResStringPool, they are converted to UTF-16 and the result is
cached for subsequent calls.
When using aapt to package, add in the "-8" switch to pack the
resources using UTF-8. This will result in the value, key, and
type strings as well as the compiled XML string values taking
significantly less space in the final application package in
most scenarios.
Change-Id: I129483f8b3d3b1c5869dced05cb525e494a6c83a
|
| |
|
| |
|
|
|