<div dir="ltr"><div><div>Hi,<br><br>Dmitry Moskalchuk from CrystaX is working on Android support for regression tests. He noted the problems with clang toolchain indication on Android:<span class="im"><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

BTW, if you&#39;ll look on<br>
<a href="http://boost.crystax.net/master/developer/summary.html" target="_blank">http://boost.crystax.net/master/developer/summary.html</a>, you&#39;ll see clang<br>
toolchains indicated as &#39;clang-linux-3.4&#39; and &#39;clang-linux-3.5&#39;. It goes<br>
from the fact that Boost build scripts suppose there are just two types<br>
of clang - clang-darwin and clang-linux, and switch between them based<br>
on host OS condition, which is wrong. It should be based on target OS.<br>
Look here:<br>
<a href="https://github.com/boostorg/build/blob/develop/src/tools/clang.jam" target="_blank">https://github.com/boostorg/build/blob/develop/src/tools/clang.jam</a>. I<br>
suppose there should be smth like this:<br>
<br>
if $(target-os) = darwin<br>
    toolset.using clang-darwin .....<br>
else if $(target-os) = linux<br>
    toolset.using clang-linux ...<br>
else if $(target-os) = android<br>
    toolset.using clang-android ....<br>
<br>
Or smth like that. I don&#39;t know bjam syntax good, so it&#39;s just to<br>
indicate my idea. I&#39;d be appreciate if you could fix this while I&#39;m<br>
finishing with scripts refactoring.<br></blockquote><div> </div></span></div>Could someone take a look into this issue and provide some fixes?<br><br></div>Probably the better solution would be to construct toolchain name from<br>$(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 toolchain+os<br><br><div><div><div>-- <br><div class="gmail_signature">Best regards,<br>Antony Polukhin</div>
</div></div></div></div>