I have a shared library that uses boost_threads and boost_system (and asio).
I can build this library with r6b and better of the NDK with the boost
configuration files to use gnustl_static (and exceptions and rtti and
pthreads.)
I would like to provide the source to this library to OEMs to build into
their system image (and provide OEM specific implementations of functions
used by the library to talk to their special hardware.)
Is there an analog to APP_STL := gnustl_static that can be used in the
external/<project>/Android.mk?
I'm sort of looking at things like adding
LOCAL_CPP_FLAGS = -nostdinc++ -pthread -fexceptions -frtti
LOCAL_C_INCLUDES :=
prebuilt/ndk/android-ndk-r6/sources/cxx-stl/gnu-libstdc++/include \
prebuilt/ndk/android-ndk-r6/sources/cxx-stl/gnu-libstdc++/libs/armeabi/include
LOCAL_LD_FLAGS :=
prebuilt/ndk/android-ndk-r6/sources/cxx-stl/gnu-libstdc++/libs/armeabi/libstdc++.a
to external/<project>/Android.mk, but it feels like that is "not the right
thing to do".
So, does anybody have a better plan, or a "how to boost/templates/rtti with
stlport" in external/projects?
Thanks for your time.
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
