replicant-frameworks_native

History

Dan Egnor 386a332b4f Make static versions of libutils and libbinder. Fix some small static-initialization-order issues (and a static- initializers-missing issue) that result from doing so. The static libraries don't actually get used for anything real at the moment -- they're used for perf tests of bug 2660235. Bug: 2660235 Change-Id: Iee2f38f79cc93b395e8d0a5a144ed92461f5ada0		2010-05-06 01:03:31 -07:00
..
Android.mk	Make static versions of libutils and libbinder.	2010-05-06 01:03:31 -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
README
RefBase.cpp
ResourceTypes.cpp
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp	Make static versions of libutils and libbinder.	2010-05-06 01:03:31 -07:00
String16.cpp
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.