Relation between app_stl values ​​with static and shared built-in android

Question

Interesting, and now confused.

When app_stl = stlport_static or stlport_shared is installed in the Application.mk file, and you are trying to create either a generic or a static version of the library. what is the effect, why do you have a specific case (see below) in your Android ndk app?

let's say that I have

Case1: APP_STL=stlport_static and include $(BUILD_SHARED_LIBRARY) 
Case2: APP_STL=stlport_static and include $(BUILD_STATIC_LIBRARY) 

Case3: APP_STL=stlport_shared and include $(BUILD_SHARED_LIBRARY) 
Case4: APP_STL=stlport_shared and include $(BUILD_STATIC_LIBRARY) 

I understand the difference between stlport and gnustl, so I am well versed in this part.

Answer 1

Case1: APP_STL = stlport_static and enable $ (BUILD_SHARED_LIBRARY)
Case 2: APP_STL = stlport_static and enable $ (BUILD_STATIC_LIBRARY)

( STLport) , , STLport. STLport, , , " " .

, doc/CPLUSPLUS-SUPPORT.html :

II.
...

II.3.
...

, , ++ .

, , , , stlport_static, .

, (, libfoo.so libbar.so), runtime, . , , / , .