replicant-frameworks_native

History

Mathias Agopian 4de4ebf6a2 use broadcast() instead of signal() when signaling the condition-variable Thread::RequestExitAndWait() is waiting for we could have several thread waiting on the condition and they all need to wake-up. also added a debug "mTid" field in the class, which contains the tid of the thread (as opposed to pthread_t), this is useful when debugging under gdb for instance.		2009-09-09 02:45:26 -07:00
..
Android.mk	implement Mutex and Condition with pthread instead of calling futex directly.	2009-07-13 15:14:23 -07:00
Asset.cpp	Fix issue #2048263 : More debugging information	2009-08-11 18:56:41 -07:00
AssetDir.cpp
AssetManager.cpp	Don't re-parse the framework resources all the time.	2009-07-06 11:12:37 -07:00
BackupData.cpp	Only restore the bits for wallpapers that aren't built in.	2009-07-29 12:05:36 -07:00
BackupHelpers.cpp	Better (and less) logging from backup.	2009-06-26 17:19:11 -04:00
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp	Make it an error to use a bare apostrophe in aapt, and adjust warnings/errors.	2009-09-01 15:20:30 -07:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp	quick fix; utf8_codepoint_count must be utf8_length	2009-07-09 13:05:24 +09:00
String16.cpp
StringArray.cpp	rename string_array.h to StringArray.h and move the implementation from the header file to a new cpp file.	2009-06-05 01:26:23 -07:00
SystemClock.cpp
TextOutput.cpp
Threads.cpp	use broadcast() instead of signal() when signaling the condition-variable Thread::RequestExitAndWait() is waiting for	2009-09-09 02:45:26 -07:00
Timers.cpp
Unicode.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
ZipUtils.cpp	fix FILE* version of ZipUtils::inflateToBuffer	2009-07-16 11:27:13 -07:00

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.