replicant-frameworks_native/libs/utils
Jeff Brown cfa6d98278 resolved conflicts for merge of f7adbe10 to master
Change-Id: I898a5e53b180adaee2337c0c0b9896c799d056e7
2010-07-16 10:06:33 -07:00
..
tests Don't build framework tests for simulator target. 2010-07-14 22:55:02 -07:00
Android.mk Add initial gamepad support. 2010-07-13 17:04:57 -07:00
Asset.cpp
AssetDir.cpp
AssetManager.cpp
BackupData.cpp
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
Debug.cpp
FileMap.cpp
Flattenable.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
ObbFile.cpp Tweak ObbFile class 2010-07-12 09:11:24 -07:00
PollLoop.cpp Add new glue code for writing native apps. 2010-07-08 11:06:59 -07:00
Pool.cpp
README
RefBase.cpp
ResourceTypes.cpp
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp Fix bug with phantom input windows. 2010-07-16 00:02:48 -07:00
String16.cpp
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp
Timers.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
ZipUtils.cpp

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.