Boost-for-Android icon indicating copy to clipboard operation
Boost-for-Android copied to clipboard

Doesn't work at all

Open rcdailey opened this issue 11 years ago • 3 comments

I'm building on Windows and no matter how many hours I spend on this thing, I can't get it to build boost. It also looks for the toolchain in the wrong path. Part of the path to the toolchain has "windows-x86" but it is installed as just "windows" in my NDK.

Here are the error logs:

$ ./build-android.sh --boost=1.55.0 $ANDROID_NDK_ROOT
To follow build in another terminal, please use: tail -F /c/code/Boost-for-Android/logs/myst-log-473520.log
Building boost version: 1.55.0
Cleaning: boost_1_55_0

etected Android NDK version 9d
Building with TOOLSET=gcc-androidR8e CXXPATH=/c/android/android-ndk-r9d/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86/bin/arm-linux-androideabi-g++ CXXFLAGS=
Unpacking boost
Performing boost bootstrap
Building Boost.Build engine with toolset ...
Failed to build Boost.Build build engine
Consult 'bootstrap.log' for more details
patching file boost/asio/detail/socket_types.hpp
patching file boost/asio/ip/impl/address_v6.ipp
patching file boost/config/user.hpp
patching file boost/interprocess/detail/workaround.hpp
patching file boost/predef/other/endian.h
patching file libs/filesystem/src/operations.cpp
# ---------------
# Build using NDK
# ---------------
Building boost for android
./build-android.sh: line 373: ./bjam: No such file or directory
ERROR: Failed to build boost for android!
Done!

rcdailey avatar Jul 10 '14 23:07 rcdailey

Hi, could you try changing the line 239 of file build-android.sh from

CXXPATH=$AndroidNDKRoot/toolchains/${TOOLCHAIN}/prebuilt/$PlatformOS-x86/bin/arm-linux-androideabi-g++ to CXXPATH=$AndroidNDKRoot/toolchains/${TOOLCHAIN}/prebuilt/$PlatformOS/bin/arm-linux-androideabi-g++

See where it takes us. Also, I haven't used cygwin in a long time so I'm probably wrong, but shouldn't the path start with /cygdrive/c/...?

inetic avatar Jul 10 '14 23:07 inetic

FYI I did create a copy and rename it to windows-x86 just to get it working. The logs I pasted are the result of that.

Yes maybe I'm not specifying paths correctly. What specifically ?​


Robert Dailey

On Thu, Jul 10, 2014 at 6:41 PM, Peter Jankuliak [email protected] wrote:

Hi, could you try changing the line 239 of file build-android.sh from

CXXPATH=$AndroidNDKRoot/toolchains/${TOOLCHAIN}/prebuilt/$PlatformOS-x86/bin/arm-linux-androideabi-g++ to

CXXPATH=$AndroidNDKRoot/toolchains/${TOOLCHAIN}/prebuilt/$PlatformOS/bin/arm-linux-androideabi-g++

See where it takes us. Also, I haven't used cygwin in a long time so I'm probably wrong, but shouldn't the path start with /cygdrive/c/...?

— Reply to this email directly or view it on GitHub https://github.com/MysticTreeGames/Boost-for-Android/issues/69#issuecomment-48678658 .

rcdailey avatar Jul 10 '14 23:07 rcdailey

You should only need to specify the path to the NDK root, which seems you've done correctly. You can try to run command

ls -l /c/android/android-ndk-r9d/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86/bin/arm-linux-androideabi-g++

to see if the path to the compiler is correct. The log you've pasted hints that there should be another log file called bootstrap.log somewhere. Can you find and paste it here?

inetic avatar Jul 11 '14 00:07 inetic