Subject: [Boost-build] Android and Clang
From: Antony Polukhin (antoshkka_at_[hidden])
Date: 2015-02-04 12:38:19
Dmitry Moskalchuk from CrystaX is working on Android support for regression
tests. He noted the problems with clang toolchain indication on Android:
BTW, if you'll look on
> http://boost.crystax.net/master/developer/summary.html, you'll see clang
> toolchains indicated as 'clang-linux-3.4' and 'clang-linux-3.5'. It goes
> from the fact that Boost build scripts suppose there are just two types
> of clang - clang-darwin and clang-linux, and switch between them based
> on host OS condition, which is wrong. It should be based on target OS.
> Look here:
> https://github.com/boostorg/build/blob/develop/src/tools/clang.jam. I
> suppose there should be smth like this:
> if $(target-os) = darwin
> toolset.using clang-darwin .....
> else if $(target-os) = linux
> toolset.using clang-linux ...
> else if $(target-os) = android
> toolset.using clang-android ....
> Or smth like that. I don't know bjam syntax good, so it's just to
> indicate my idea. I'd be appreciate if you could fix this while I'm
> finishing with scripts refactoring.
Could someone take a look into this issue and provide some fixes?
Probably the better solution would be to construct toolchain name from
$(toolset-base-name)-$(target-os)-$(toolset-version)? This could fix all
the names of clang/gcc/intel compilers on Android/QNX/iOS platforms and
simplify the task of updating explicit-failures-markup.xml for a specific
-- Best regards, Antony Polukhin
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk