It looks like the build system doesn't see Boost root... If you add
<cxxflags>-I/full/path/to/Boost does it help?
Note that most of Boost libraries are header-only, and you don't have
to build them. So the above list of built libraries includes almost
all the libs, which need to be built.
Copying extra files into the NDK platform directory is not really a good idea. It is best to keep the boost headers as part of your project or in a separate directory and include the path in your android.mk file as a -I compiler flag. Also, some parts of boost may require exceptions and rtti, so you should use the gnustl_static STL implementation. Just add a line like APP_STL := gnustl_static to your Application.mk file.
> cheers
> sdy7
>
> --
> You received this message because you are subscribed to the Google Groups "android-ndk" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-ndk...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-ndk?hl=en.
>
i am not sure you can succesfuuly compile boost with andoid -ndk 5 even of it have stl support
use android-ndk r4-crystax with all support for boost , since i am not sure c++ excption is handled in android-ndk r5
pleas
On Sat, Dec 18, 2010 at 12:46 PM, Nasif Noorudeen <nas...@gmail.com> wrote:i am not sure you can succesfuuly compile boost with andoid -ndk 5 even of it have stl support
use android-ndk r4-crystax with all support for boost , since i am not sure c++ excption is handled in android-ndk r5
pleas
That's why you need to use the "APP_STL := gnustl_static" flag in your Application.mk file. This uses the GNU STL implementation which does support exceptions and RTTI, unlike the other STL implementations that come with the NDK.
On 12/20/2010 12:59 AM, Afriza N. Arief wrote:
> Other thread reports that using gnustl_static may cause your app to work
> only on Android 2.2+ and when using crystax, it should run on Android 2.0.1+
Crystax works all the way back to (at least) 1.5.
Still waiting on upgrading to r5 for verification that it WILL work at
least back to 1.6.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNEAT+AAoJENSbqLBCyKKsnsYH/AkVzKCEBe2iPRLHXwV558ed
5Ij8cS5HEJQTy6f6bIJiTrtS6Ey926/tY1kmFZ4aXnYCrCNXmyUc01jI7h0dP6SC
KOfQOmx7dIr0S9QsFzBYxa/x2SEHf8u7wlf8wqfDeBqJ4WqvttSO379/IyNilSHH
T+TKlJKNhacP2iaiMZTUfE3yKn9nrqcimv5hpiMsKk3WWXm+mEkKuTSHrbvUMjMp
IrTJiuVMxDh5CrmGjYgpKHwx78EaZ+i/SdaW4x/QAJjquePc90fNJ4P8flFK505c
sTidn11j3yHryqQz3+2AmIuCZU9xE4tkhn0nmbDrIyN4nBNwFZ8D0M0xoXYdm7c=
=mla7
-----END PGP SIGNATURE-----