replicant-frameworks_native/libs/utils
Dianne Hackborn 878d647b5b am b8546001: Merge change 20878 into donut
Merge commit 'b8546001701405a76dad7e6235046e592296fac2'

* commit 'b8546001701405a76dad7e6235046e592296fac2':
  Fix issue #2048263: More debugging information
2009-08-12 12:36:12 -07:00
..
Android.mk
Asset.cpp Fix issue #2048263: More debugging information 2009-08-11 18:56:41 -07:00
AssetDir.cpp
AssetManager.cpp
BackupData.cpp Only restore the bits for wallpapers that aren't built in. 2009-07-29 12:05:36 -07:00
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp Fix #2018814: System cannot correctly render assets with "wrap_content" attribute in QVGA 2009-07-29 19:44:01 -07:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp
String16.cpp
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp Fix Win32 libutils to get a working SDK build. 2009-08-01 10:53:29 +02:00
Timers.cpp
Unicode.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
ZipUtils.cpp fix FILE* version of ZipUtils::inflateToBuffer 2009-07-16 11:27:13 -07:00

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.