da416411e0
Move Pipe and executablepath from libutils to the simulator, since nothing else uses them. |
||
---|---|---|
.. | ||
Android.mk | ||
Asset.cpp | ||
AssetDir.cpp | ||
AssetManager.cpp | ||
backup_data.cpp | ||
backup_helper_file.cpp | ||
BufferedTextOutput.cpp | ||
CallStack.cpp | ||
characterData.h | ||
Debug.cpp | ||
FileMap.cpp | ||
futex_synchro.c | ||
InetAddress.cpp | ||
LogSocket.cpp | ||
misc.cpp | ||
MODULE_LICENSE_APACHE2 | ||
NOTICE | ||
ported.cpp | ||
README | ||
RefBase.cpp | ||
ResourceTypes.cpp | ||
SharedBuffer.cpp | ||
Socket.cpp | ||
Static.cpp | ||
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.