AMDG On 02/04/2018 11:13 AM, John Maddock via Boost wrote:
I have, and have had for some time:
using msvc : 14.0 : "C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/cl.exe" ;
Does it work if you add <rewrite-setup-scripts>off (as the next argument after the compiler)?
In my user-config.jam
However, with current develop this leads to the linker step always failing:
msvc.manifest ..\..\..\bin.v2\libs\config\test\config_info.test\msvc-14.0s11\debug\address-model-64\link-static\runtime-link-static\config_info.exe
'mt' is not recognized as an internal or external command, operable program or batch file.
if exist "..\..\..\bin.v2\libs\config\test\config_info.test\msvc-14.0s11\debug\address-model-64\link-static\runtime-link-static\config_info.exe.manifest" ( call "..\..\..\bin.v2\standalone\msvc\msvc-14.0s11\address-model-64\architecture-x86\msvc-setup.bat" amd64 >nul mt -nologo -manifest "..\..\..\bin.v2\libs\config\test\config_info.test\msvc-14.0s11\debug\address-model-64\link-static\runtime-link-static\config_info.exe.manifest" "-outputresource:..\..\..\bin.v2\libs\config\test\config_info.test\msvc-14.0s11\debug\address-model-64\link-static\runtime-link-static\config_info.exe;1"
)
As you can see no tool name is set on the start of the command line.
Anyone any ideas?
The command line looks right. Check the contents of msvc-setup.bat. In Christ, Steven Watanabe