History log of /ndk/tests/build/gnustl-force-rtti/jni/forced_rtti.cpp
Revision Date Author Comments
247678f25163a841b4a7d48745a75bff5ed0f863 13-Jan-2012 David 'Digit' Turner <digit@google.com> Fix the compilation of two unit tests.

These tests do compile find with GCC 4.4.3, but they failed loudly when
trying to rebuild them with GCC 4.6

Change-Id: I04041a5eae14401a02bfe96c8f43c0c1273327c2
e80e45babf627adfeb5bb5fc8bc02cb5076b3ce4 23-Dec-2011 David 'Digit' Turner <digit@google.com> Do not force exceptions and rtti when using GNU libstdc++

This patch changes the default exported flags for both
gnustl_static and gnustl_shared. Previously, they were always
set to -fexceptions and -frtti, but this resulted in a few
problems.

Now, the flags are empty by default, but you can use
APP_GNUSTL_FORCE_CPP_FEATURES in your Application.mk to
revert to the old behaviour, in case you need it.

+ Add four unit tests to check that the build system works
correctly with regards to this new variable definition

+ Documentation updates.

+ Modify tests/run-tests.sh to recognize a 'BUILD_SHOULD_FAIL'
tag in a unit test directory. If such a file is present,
the build _should_ fail for the test to pass.

This is required because there is no way to reliably detect
at compile time that -frtti is _not_ used, so we actually
require the opposite from our unit test sources.
(see gnustl-force-none and gnustl-force-exceptions).

Change-Id: Ia6fd236284c942bc0cb8fc0b49d9344ab68fe7ee