replicant-frameworks_native

History

Kenny Root ccb5b89029 Add string resource type inspection Allows "aapt dump --values resource" to print out whether a string in a ResStringPool is in UTF-8 or UTF-16 encoding. Change-Id: I6478884a70a3b46fee862dece6cb33454fc34843		2009-12-10 14:22:08 -08:00
..
Android.mk	implement Mutex and Condition with pthread instead of calling futex directly.	2009-07-13 15:14:23 -07:00
Asset.cpp	Fix issue #2048263 : More debugging information	2009-08-11 18:56:41 -07:00
AssetDir.cpp
AssetManager.cpp	Don't re-parse the framework resources all the time.	2009-07-06 11:12:37 -07:00
BackupData.cpp	Turn off most of the backup-related debug logging	2009-09-30 17:07:37 -07:00
BackupHelpers.cpp	Better (and less) logging from backup.	2009-06-26 17:19:11 -04:00
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h	rename a few files to camel-case, add copyright notices	2009-06-04 13:53:57 -07:00
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp	Add string resource type inspection	2009-12-10 14:22:08 -08:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp	Optional use of UTF-8 strings in resource bundles	2009-12-07 15:14:15 -08:00
String16.cpp	Optional use of UTF-8 strings in resource bundles	2009-12-07 15:14:15 -08:00
StringArray.cpp	rename string_array.h to StringArray.h and move the implementation from the header file to a new cpp file.	2009-06-05 01:26:23 -07:00
SystemClock.cpp
TextOutput.cpp
Threads.cpp	Maybe really fix windows build.	2009-12-08 19:45:59 -08:00
Timers.cpp
Unicode.cpp	rename a few files to camel-case, add copyright notices	2009-06-04 13:53:57 -07:00
VectorImpl.cpp
ZipFileCRO.cpp	rename a few files to camel-case, add copyright notices	2009-06-04 13:53:57 -07:00
ZipFileRO.cpp	rename a few files to camel-case, add copyright notices	2009-06-04 13:53:57 -07:00
ZipUtils.cpp	fix FILE* version of ZipUtils::inflateToBuffer	2009-07-16 11:27:13 -07:00

README

Android Utility Function Library

If you need a feature that is native to Linux but not present on other
platforms, construct a platform-dependent implementation that shares
the Linux interface.  That way the actual device runs as "light" as
possible.

If that isn't feasible, create a system-independent interface and hide
the details.

The ultimate goal is *not* to create a super-duper platform abstraction
layer.  The goal is to provide an optimized solution for Linux with
reasonable implementations for other platforms.