Oliver, thank you for your answer.
But clang does recognize '-c' on Windows as it uses it to compile all
other files.
When I invoke b2.exe with "toolset=msvc-14.0", the command looks like this:
ml64 -nologo -c -Zp4 -Cp -Cx -DBOOST_ALL_NO_LIB=1
-DBOOST_CONTEXT_EXPORT= -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS
-DNDEBUG -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_EXPORT=
-DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG /W3 -Fo
"D:\path\to\boost\bin.v2\libs\context\build\msvc-14.0\release\address-model-64\link-static\runtime-link-static\threading-multi\asm\make_x86_64_ms_pe_masm.obj"
"D:\path\to\boost\libs\context\src\asm\make_x86_64_ms_pe_masm.asm"
But when "toolset=clang-win" the command becomes:
-c -Zp4 -Cp -Cx -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE
-DBOOST_DISABLE_ASSERTS -DNDEBUG -DBOOST_ALL_NO_LIB=1
-DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG /W3 -Fo
"D:\path\to\boost\bin.v2\libs\context\build\clang-vc14-win\release\link-static\runtime-link-static\threading-multi\asm\make_x86_64_ms_pe_gas.obj"
"D:\path\to\boost\libs\context\src\asm\make_x86_64_ms_pe_gas.asm"
I see two problems here:
1) BB does not know the name of assembler when clang-win is used;
2) BB tries to use command arguments from ml64.exe (all those -Zp4,
-Cp and -Fo belong to Microsoft Assembler) to compile gas source.
2017-02-05 14:17 GMT+03:00 Oliver Kowalke
2017-02-05 11:33 GMT+01:00 Mikhail Strelnikov
: '-c' is not recognized as an internal or external command,
clang on Win does not recognize cmd line option '-c' that might be set by boost.build
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users