Issue with bjam and building for NDK
I filed an issue over at the Android NDK github page here: https://github.com/android-ndk/ndk/issues/616 When I invoke b2 to build boost using the standalone toolchain generated by the NDK, bjam seems to be wrapping the command in quotes, like "clang++". This throws off their logic in the clang++.cmd batch script. I was asked to test running b2 without quotes (e.g. clang++), but I am not sure how to do this. Could someone help me understand if this is a code change to b2? Or if there's a jam script somewhere I can modify? I'm not sure if this is a boost issue or an NDK issue at this point. I appreciate any help from the boost developers.
AMDG On 01/11/2018 03:31 PM, Robert Dailey via Boost wrote:
I filed an issue over at the Android NDK github page here: https://github.com/android-ndk/ndk/issues/616
When I invoke b2 to build boost using the standalone toolchain generated by the NDK, bjam seems to be wrapping the command in quotes, like "clang++". This throws off their logic in the clang++.cmd batch script. I was asked to test running b2 without quotes (e.g. clang++), but I am not sure how to do this.
Could someone help me understand if this is a code change to b2?
Yes it's a change. It was done in order to handle the case where the path to clang++ contains spaces. https://github.com/boostorg/build/commit/c442d64b30a585ca114a1cb8c5ed8b33a93...
Or if there's a jam script somewhere I can modify?
tools/build/src/tools/clang-linux.jam Search for "$(CONFIG_COMMAND)"
I'm not sure if this is a boost issue or an NDK issue at this point. I appreciate any help from the boost developers.
In Christ, Steven Watanabe
participants (2)
-
Robert Dailey -
Steven Watanabe