replicant-frameworks_native

History

Jeff Brown cfa6d98278 resolved conflicts for merge of f7adbe10 to master Change-Id: I898a5e53b180adaee2337c0c0b9896c799d056e7		2010-07-16 10:06:33 -07:00
..
tests
Android.mk
Asset.cpp
AssetDir.cpp
AssetManager.cpp
BackupData.cpp
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp	some work to try to reduce the code size of some native libraries	2009-05-26 16:12:20 -07:00
Debug.cpp
FileMap.cpp
Flattenable.cpp	remove a dependency of GraphicBuffer (libui) on Parcel (libbinder).	2010-02-21 23:27:25 -08:00
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
ObbFile.cpp
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
String16.cpp	Optional use of UTF-8 strings in resource bundles	2009-12-07 15:14:15 -08:00
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp
Timers.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
ZipUtils.cpp

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.