replicant-frameworks_native/libs/utils
Marco Nelissen 8f9ede0f6d am 7198030f: This should fix the simulator build.
Merge commit '7198030fce4b54820a65a10d54fae18a1ab5df84'

* commit '7198030fce4b54820a65a10d54fae18a1ab5df84':
  This should fix the simulator build.
2009-05-22 12:30:07 -07:00
..
Android.mk checkpoint: split libutils into libutils + libbinder 2009-05-20 12:55:02 -07:00
Asset.cpp
AssetDir.cpp
AssetManager.cpp
backup_data.cpp
backup_helper_file.cpp
BufferedTextOutput.cpp
CallStack.cpp
characterData.h
Debug.cpp
executablepath_darwin.cpp
executablepath_linux.cpp
FileMap.cpp
futex_synchro.c This should fix the simulator build. 2009-05-22 12:25:56 -07:00
InetAddress.cpp
LogSocket.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
Pipe.cpp
ported.cpp
README
RefBase.cpp
ResourceTypes.cpp
SharedBuffer.cpp
Socket.cpp
Static.cpp checkpoint: split libutils into libutils + libbinder 2009-05-20 12:55:02 -07:00
StopWatch.cpp
String8.cpp
String16.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp
TimerProbe.cpp
Timers.cpp
Unicode.cpp
VectorImpl.cpp
ZipEntry.cpp
ZipFile.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.