Time for action – compiling an executable linked to Boost

Let's use the Boost unit test library to build our own unit test executable through the following steps:

1. Still in the boost directory, create a new Android.mk file to declare the newly prebuilt libraries as Android modules and make them available to NDK applications. This file needs to contain one module declaration per library. For example, define one module boost_unit_test_framework:
   • LOCAL_SRC_FILES reference the static library libboost_unit_test_framework.a we have built with b2.

   Use the $(TARGET_ARCH_ABI) variable to determine the right path to use, which depends on the target platform. Its value can be armeabi, armeabi-v7a, or x86. If you compile DroidBlaster for X86, the NDK will look for libboost_unit_test_framework.a in androidx86/lib.

   • LOCAL_EXPORT_C_INCLUDES automatically appends boost root directory to the include file directory list of the including module.
   • Indicate that this module is a prebuilt library with the...