android的ndk里面编译boost

一：背景

工作需要，要在android里面使用boost库，但是使用方法不是供界面通过jni的方法调用，

而是只需要编译以后供c/c++的应用程序调用就好。

平台使用的是atom的，所以本来如果不求甚解的话，我可以直接使用linux下的编译方法，

通过静态编译就可以开发应用程序了；但是为了更好了的理解ndk，我还是决定要在ndk下面编

译通过。

二：

首先遇到的问题是，ndk下载以后不知道如何编译新的程序，也就是不知道要把boost放在

哪个目录线面编译？https://github.com/MysticTreeGames/Boost-for-Android里面也没有介绍，

可能对人家很简单吧。后来也是在一个老外的网站上

http://www.codexperiments.com/android/2011/05/tips-tricks-building-boost-with-ndk-r5/comment-page-1/#comment-336

看到需要把目录放在source下面：）。

接着就是修改编译脚本，上面地址下载的是arm的编译脚本，需要修改为x86的工具链。所以除非

运气特别好，有完全适用的，否则一般都需要自己仔细读脚本进行修改。附件是我修改的一些脚本。

#!/bin/sh# Copyright (C) 2010 Mystic Tree Games## Licensed under the Apache License, Version 2.0 (the "License");# you may not use this file except in compliance with the License.# You may obtain a copy of the License at##      http://www.apache.org/licenses/LICENSE-2.0## Unless required by applicable law or agreed to in writing, software# distributed under the License is distributed on an "AS IS" BASIS,# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.# See the License for the specific language governing permissions and# limitations under the License.## Author: Moritz "Moss" Wundke ([e-mail])## <License>## Build boost for android completly. It will download boost 1.45.0# prepare the build system and finally build it for android# Add common build methods. `dirname $0`/build-common.sh# -----------------------# Command line arguments# -----------------------BOOST_VER1=1BOOST_VER2=49BOOST_VER3=0ANDROIDNDKROOT="/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1"register_option "--boost=<version>" boost_version "Boost version to be used, one of {1.53.0,1.49.0, 1.48.0, 1.45.0}, default is 1.53.0."boost_version(){  if [ "$1" = "1.53.0" ]; then    BOOST_VER1=1    BOOST_VER2=53    BOOST_VER3=0  elif [ "$1" = "1.49.0" ]; then    BOOST_VER1=1    BOOST_VER2=49    BOOST_VER3=0  elif [ "$1" = "1.48.0" ]; then    BOOST_VER1=1    BOOST_VER2=48    BOOST_VER3=0  elif [ "$1" = "1.45.0" ]; then    BOOST_VER1=1    BOOST_VER2=45    BOOST_VER3=0  else    echo "Unsupported boost version '$1'."    exit 1  fi}CLEAN=noregister_option "--clean"    do_clean     "Delete all previously downloaded and built files, then exit."do_clean () { CLEAN=yes; }DOWNLOAD=noregister_option "--download" do_download  "Only download required files and clean up previus build. No build will be performed."do_download (){DOWNLOAD=yes# Clean previus stuff too!CLEAN=yes}LIBRARIES=--with-libraries=date_time,filesystem,program_options,regex,signals,system,thread,iostreamsregister_option "--with-libraries=<list>" do_with_libraries "Comma separated list of libraries to build."do_with_libraries () { LIBRARIES="--with-libraries=$1"; }register_option "--without-libraries=<list>" do_without_libraries "Comma separated list of libraries to exclude from the build."do_without_libraries () { LIBRARIES="--without-libraries=$1"; }PROGRAM_PARAMETERS="<ndk-root>"PROGRAM_DESCRIPTION=\"       Boost For Android\n"\"Copyright (C) 2010 Mystic Tree Games\n"\extract_parameters $@echo "Building boost version: $BOOST_VER1.$BOOST_VER2.$BOOST_VER3"# -----------------------# Build constants# -----------------------BOOST_DOWNLOAD_LINK="http://downloads.sourceforge.net/project/boost/boost/$BOOST_VER1.$BOOST_VER2.$BOOST_VER3/boost_${BOOST_VER1}_${BOOST_VER2}_${BOOST_VER3}.tar.bz2?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fboost%2Ffiles%2Fboost%2F${BOOST_VER1}.${BOOST_VER2}.${BOOST_VER3}%2F&ts=1291326673&use_mirror=garr"BOOST_TAR="boost_${BOOST_VER1}_${BOOST_VER2}_${BOOST_VER3}.tar.bz2"BOOST_DIR="boost_${BOOST_VER1}_${BOOST_VER2}_${BOOST_VER3}"BUILD_DIR="./build/"# -----------------------if [ $CLEAN = yes ] ; thenecho "Cleaning: $BUILD_DIR"rm -f -r $PROGDIR/$BUILD_DIRecho "Cleaning: $BOOST_DIR"rm -f -r $PROGDIR/$BOOST_DIRecho "Cleaning: $BOOST_TAR"rm -f $PROGDIR/$BOOST_TARecho "Cleaning: logs"rm -f -r logsrm -f build.log  [ "$DOWNLOAD" = "yes" ] || exit 0fi# It is almost never desirable to have the boost-X_Y_Z directory from# previous builds as this script doesn't check in which state it's# been left (bootstrapped, patched, built, ...). Unless maybe during# a debug, in which case it's easy for a developer to comment out# this code.if [ -d "$PROGDIR/$BOOST_DIR" ]; thenecho "Cleaning: $BOOST_DIR"# rm -f -r $PROGDIR/$BOOST_DIRfiif [ -d "$PROGDIR/$BUILD_DIR" ]; thenecho "Cleaning: $BUILD_DIR"# rm -f -r $PROGDIR/$BUILD_DIRfiexport AndroidNDKRoot=$PARAMETERSif [ -z "$AndroidNDKRoot" ] ; thenif [ -z "`which ndk-build`" ]; thendump "ERROR: You need to provide a <ndk-root>!"exit 1fiAndroidNDKRoot=`which ndk-build`AndroidNDKRoot=`dirname $AndroidNDKRoot`echo "Using AndroidNDKRoot = $AndroidNDKRoot"fi# Check platform patchcase "$HOST_OS" in    linux)        Platfrom=linux-x86        ;;    darwin|freebsd)        Platfrom=darwin-x86        ;;    windows|cygwin)        Platfrom=windows-x86        ;;    *)  # let's play safe here        Platfrom=linux-x86esacNDK_RELEASE_FILE=$AndroidNDKRoot"/RELEASE.TXT"NDK_RN=`cat $NDK_RELEASE_FILE | sed 's/^r\(.*\)$/\1/g'`echo "Detected Android NDK version $NDK_RN"case "$NDK_RN" in4*)CXXPATH=$AndroidNDKRoot/build/prebuilt/$Platfrom/arm-eabi-4.4.0/bin/arm-eabi-g++TOOLSET=gcc-androidR4;;5*)CXXPATH=$AndroidNDKRoot/toolchains/arm-linux-androideabi-4.4.3/prebuilt/$Platfrom/bin/arm-linux-androideabi-g++TOOLSET=gcc-androidR5;;7-crystax-5.beta3)EABI_VER=4.6.3CXXPATH=$AndroidNDKRoot/toolchains/arm-linux-androideabi-$EABI_VER/prebuilt/$Platfrom/bin/arm-linux-androideabi-g++TOOLSET=gcc-androidR7crystax5beta3;;8)#CXXPATH=$AndroidNDKRoot/toolchains/arm-linux-androideabi-4.4.3/prebuilt/$Platfrom/bin/arm-linux-androideabi-g++CXXPATH=/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/toolchains/x86-4.7/prebuilt/linux-x86/bin/i686-linux-android-g++TOOLSET=gcc-androidR8#TOOLSET=/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/toolchains/x86-4.7/prebuilt/linux-x86/bin/i686-linux-android-g++;;8b|8c|8d)CXXPATH=$AndroidNDKRoot/toolchains/arm-linux-androideabi-4.6/prebuilt/$Platfrom/bin/arm-linux-androideabi-g++TOOLSET=gcc-androidR8b;;8e)CXXPATH=$AndroidNDKRoot/toolchains/arm-linux-androideabi-4.6/prebuilt/$Platfrom/bin/arm-linux-androideabi-g++TOOLSET=gcc-androidR8e;;*)echo "Undefined or not supported Android NDK version!"exit 1esacecho Building with TOOLSET=$TOOLSET CXXPATH=$CXXPATH CXXFLAGS=$CXXFLAGS | tee $PROGDIR/build.log# Check if the ndk is valid or notif [ ! -f $CXXPATH ]thenecho "Cannot find C++ compiler at: $CXXPATH"exit 1fi# -----------------------# Download required files# -----------------------# Downalod and unzip boost in a temporal folder andif [ ! -f $BOOST_TAR ]thenecho "Downloading boost ${BOOST_VER1}.${BOOST_VER2}.${BOOST_VER3} please wait..."prepare_download#download_file $BOOST_DOWNLOAD_LINK $PROGDIR/$BOOST_TARfiif [ ! -f $PROGDIR/$BOOST_TAR ]thenecho "Failed to download boost! Please download boost ${BOOST_VER1}.${BOOST_VER2}.${BOOST_VER3} manually\nand save it in this directory as $BOOST_TAR"exit 1fiif [ ! -d $PROGDIR/$BOOST_DIR ]thenecho "Unpacking boost"# tar xjf $PROGDIR/$BOOST_TARfiif [ $DOWNLOAD = yes ] ; thenecho "All required files has been downloaded and unpacked!"exit 0fi# ---------# Bootstrap# ---------if [ ! -f ./$BOOST_DIR/bjam ]then  # Make the initial bootstrap  echo "Performing boost bootstrap"  cd $BOOST_DIR   ./bootstrap.sh --prefix="./../$BUILD_DIR/"      \                 $LIBRARIES                       \                 2>&1 | tee -a $PROGDIR/build.log  if [ $? != 0 ] ; then  dump "ERROR: Could not perform boostrap! See $TMPLOG for more info."  exit 1  fi  cd $PROGDIR    # -------------------------------------------------------------  # Patching will be done only if we had a successfull bootstrap!  # -------------------------------------------------------------  # Apply patches to boost  BOOST_VER=${BOOST_VER1}_${BOOST_VER2}_${BOOST_VER3}  PATCH_BOOST_DIR=$PROGDIR/patches/boost-${BOOST_VER}  cp configs/user-config-boost-${BOOST_VER}.jam $BOOST_DIR/tools/build/v2/user-config.jam  for dir in $PATCH_BOOST_DIR; do    if [ ! -d "$dir" ]; then      echo "Could not find directory '$dir' while looking for patches"      exit 1    fi    PATCHES=`(cd $dir && ls *.patch | sort) 2> /dev/null`    if [ -z "$PATCHES" ]; then      echo "No patches found in directory '$dir'"      exit 1    fi    for PATCH in $PATCHES; do      PATCH=`echo $PATCH | sed -e s%^\./%%g`      SRC_DIR=$PROGDIR/$BOOST_DIR      PATCHDIR=`dirname $PATCH`      PATCHNAME=`basename $PATCH`      log "Applying $PATCHNAME into $SRC_DIR/$PATCHDIR"      cd $SRC_DIR && patch -p1 < $dir/$PATCH && cd $PROGDIR      if [ $? != 0 ] ; then        dump "ERROR: Patch failure !! Please check your patches directory!"        dump "       Try to perform a clean build using --clean ."        dump "       Problem patch: $dir/$PATCHNAME"        exit 1      fi    done  donefiecho "# ---------------"echo "# Build using NDK"echo "# ---------------"# Build boost for androidecho "Building boost for android"(  cd $BOOST_DIR  export PATH=`dirname $CXXPATH`:$PATH  export AndroidNDKRoot=$AndroidNDKRoot  export NO_BZIP2=1  cxxflags=""  for flag in $CXXFLAGS; do cxxflags="$cxxflags cxxflags=$flag"; done  ./b2 -q                           \--build-type=complete      \         toolset=$TOOLSET             \         $cxxflags                    \         link=shared \         threading=multi              \         --layout=versioned           \         install 2>&1                 \         | tee -a $PROGDIR/build.log  if [ ${PEPESTATUS[0]} != 0 ] ; then    dump "ERROR: Failed to build boost for android!"    exit 1  fi)dump "Done!"

另外一个是：

# Copyright 2003, 2005 Douglas Gregor# Copyright 2004 John Maddock# Copyright 2002, 2003, 2004, 2007 Vladimir Prus# Distributed under the Boost Software License, Version 1.0.# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)#   This file is used to configure your Boost.Build installation. You can modify# this file in place, or you can place it in a permanent location so that it# does not get overwritten should you get a new version of Boost.Build. See:##   http://www.boost.org/boost-build2/doc/html/bbv2/overview/configuration.html## for documentation about possible permanent locations.#   This file specifies which toolsets (C++ compilers), libraries, and other# tools are available. Often, you should be able to just uncomment existing# example lines and adjust them to taste. The complete list of supported tools,# and configuration instructions can be found at:##   http://boost.org/boost-build2/doc/html/bbv2/reference/tools.html##   This file uses Jam language syntax to describe available tools. Mostly,# there are 'using' lines, that contain the name of the used tools, and# parameters to pass to those tools -- where paremeters are separated by# semicolons. Important syntax notes:##   - Both ':' and ';' must be separated from other tokens by whitespace#   - The '\' symbol is a quote character, so when specifying Windows paths you#     should use '/' or '\\' instead.## More details about the syntax can be found at:##   http://boost.org/boost-build2/doc/html/bbv2/advanced.html#bbv2.advanced.jam_language## ------------------# Android configurations.# ------------------using gcc : androidR8:i686-linux-android-g++:<archiver>i686-linux-android-ar<compileflags>-fexceptions<compileflags>-frtti<compileflags>-fpic<compileflags>-ffunction-sections<compileflags>-funwind-tables<compileflags>-Wno-psabi<compileflags>-march=atom<compileflags>-mtune=atom<compileflags>-msoft-float<compileflags>-Os<compileflags>-fomit-frame-pointer<compileflags>-fno-strict-aliasing<compileflags>-finline-limit=64<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/platforms/android-9/arch-x86/usr/include#<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/platforms/android-9/arch-x86/usr/include/machine/<compileflags>-Wa,--noexecstack<compileflags>-DANDROID<compileflags>-D__ANDROID__<compileflags>-DNDEBUG<compileflags>-O2<compileflags>-g#<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/sources/cxx-stl/stlport/stlport/<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/sources/crystax/include<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/sources/cxx-stl/gnu-libstdc++/4.4.3/include<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/sources/cxx-stl/gnu-libstdc++/4.4.3/libs/x86/include<compileflags>-L/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/platforms/android-9/arch-x86/usr/lib/#<compileflags>-I/home/wy/intel-x86/work/ndk_boost/android-ndk-r8-crystax-1/sources/cxx-stl/gnu-libstdc++/4.4.3/include/tr1/# @Moss - Above are the 'oficial' android flags<architecture>x86<compileflags>-fvisibility=hidden<compileflags>-fvisibility-inlines-hidden<compileflags>-fdata-sections<cxxflags>-D_REENTRANT<cxxflags>-D_GLIBCXX__PTHREADS;# --------------------------------------------------------------------# Is same for 8b, 8c and 8d

结果如下：

libboost_chrono-gcc-mt-1_49.a      libboost_math_tr1f-gcc-mt-1_49.a         libboost_signals-gcc-mt-1_49.alibboost_date_time-gcc-mt-1_49.a   libboost_math_tr1-gcc-mt-1_49.a          libboost_system-gcc-mt-1_49.alibboost_exception-gcc-mt-1_49.a   libboost_math_tr1l-gcc-mt-1_49.a         libboost_test_exec_monitor-gcc-mt-1_49.alibboost_filesystem-gcc-mt-1_49.a  libboost_prg_exec_monitor-gcc-mt-1_49.a  libboost_thread-gcc-mt-1_49.alibboost_graph-gcc-mt-1_49.a       libboost_program_options-gcc-mt-1_49.a   libboost_timer-gcc-mt-1_49.alibboost_iostreams-gcc-mt-1_49.a   libboost_python-gcc-mt-1_49.a            libboost_unit_test_framework-gcc-mt-1_49.alibboost_math_c99f-gcc-mt-1_49.a   libboost_random-gcc-mt-1_49.a            libboost_wave-gcc-mt-1_49.alibboost_math_c99-gcc-mt-1_49.a    libboost_regex-gcc-mt-1_49.a             libboost_wserialization-gcc-mt-1_49.alibboost_math_c99l-gcc-mt-1_49.a   libboost_serialization-gcc-mt-1_49.a