Ok, I am sharing my build.bat user-config-android.jam file below, from the outputs, clang is using mingw headers, for clang build, is mingw headers really necessary?
build.bat:
set CXXFLAGS="-I%ANDROID_NDK%/platforms/android-9/arch-arm/usr/include -I%ANDROID_NDK%/sources/cxx-stl/gnu-libstdc++/4.9/include -I%ANDROID_NDK%/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi/include"
set TOOLSET=gcc-android
b2 --toolset=%TOOLSET% --user-config=./user-config-android.jam cxxflags=%CXXFLAGS% threadapi=pthread --prefix=..\boost_android_arm --builddir=./ target-os=linux --with-date_time --with-filesystem --with-regex --with-log define=BOOST_FILESYSTEM_VERSION=3 --with-program_options --with-signals --with-system --with-thread link=static runtime-link=shared threading=multi install
user-config-android.jam:
androidNDKRoot = android-ndk-r10e ; # put the relevant path
using clang : android :
$(androidNDKRoot)/toolchains/llvm-3.6/prebuilt/windows-x86_64/bin/clang++ :
<compileflags>--sysroot=$(androidNDKRoot)/platforms/android-21/arch-arm
<compileflags>-Os
<compileflags>-fno-strict-aliasing
<compileflags>-O2
<compileflags>-DNDEBUG
<compileflags>-g
<compileflags>-I$(androidNDKRoot)/sources/cxx-stl/gnu-libstdc++/4.9/include
<compileflags>-I$(androidNDKRoot)/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi/include
<compileflags>-D__GLIBC__
<compileflags>-D__ANDROID__
<compileflags>-D_GLIBCXX__PTHREADS
<compileflags>-D__arm__
<compileflags>-D_REENTRANT
And I'am getting this error:
g++: error: unrecognized command line option '-stdlib=libc++'
clang++.exe: error: linker (via gcc) command failed with exit code 1 (use -v to see invocation)
"android-ndk-r10e/toolchains/llvm-3.6/prebuilt/windows-x86_64/bin/clang++" -o "bin.v2\libs\date_time\build\clang-linux-andr
oid\release\target-os-android\threadapi-pthread\threading-multi\libboost_date_time-clang-mt-1_60.so.1.60.0" -Wl,-soname -Wl,libboost_date_time-clang-m
t-1_60.so.1.60.0 -shared -Wl,--start-group "bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-mult
i\gregorian\greg_month.o" "bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\gregorian\greg_
weekday.o" "bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\gregorian\date_generators.o"
-Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group -stdlib=libc++ -lc++_shared -Landroid-ndk-r10e/sources/cxx-stl/llvm-libc++/libs/ar
meabi
...failed clang-linux.link.dll bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\libboost_da
te_time-clang-mt-1_60.so.1.60.0...
...skipped
Has anyone built the Boost with Clang and NDK other than CryStax? If so, can you post the related config.jam and build script? I have handled gcc build but clang is very very chalnllenging and no one including the guys in Stackoverflow could answer it.
I haven't noticed any problems building boost for Android with the NDK, I honestly have no idea why I see so many people asking how to do it, or patch sets or whatever. I'm using gcc-4.9 and std=c++14 on linux x64 targeting armv7. I package the toolset I want (android 15, gcc-4.9) and pass that sysroot in the CXXFLAGS, I tend not to interfere with the build system of boost or android very much, preferring to drive everything from cmake (for my own projects). What problems have you seen? The NDK is moving entirely to clang, the next release will see gcc deprecated, so I'll have to have a play with moving over to clang, but in my experience, everything I do works equally well on clang for armv7, armv8 and x64. The only problem I remember having is thread locals on iOS targets, but my memory is short, and it only takes a few lines of code to emulate that for most purposes. If you explain what problems you've seen, which libraries, toolsets and command lines, perhaps you'll trigger a memory of a problem I've solved. I can give you more details of my configuration on the weekend, if required. As a sidenote, I'm hoping to bring up a boost/clang/linux/armv8 build bot if and when my Pine64 arrives and I get Ubuntu/Debian running on it (by April if all goes well). I have no idea how quickly it will cycle though, my current x64 tests take around 16 hours for gcc-4.9, gcc-5.2 and clang-3.7, I'll probably have to drop gcc-4.9. I had to give up on my regular sanitizer builds on x64 as they just take too long and there seemed to be very little interest. Unfortunately I don't have dedicated machines to run the tests. Ben _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost