Re: [boost] [system] [teeks99] Mass test failures on MSVC-14.0

Subject: Re: [boost] [system] [teeks99] Mass test failures on MSVC-14.0
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2018-02-28 16:42:39

On 02/26/18 23:55, Tom Kent via Boost wrote:
> On Mon, Feb 26, 2018 at 11:12 AM, Daniela Engert via Boost <
> boost_at_[hidden]> wrote:
> 
>> Am 26.02.2018 um 15:52 schrieb Andrey Semashev via Boost:
>>> On 02/26/18 17:20, Tom Kent wrote:
>>
>>>
>>> 'mt' is not recognized as an internal or external command,
>>> operable program or batch file.
>>> ...failed msvc.manifest.dll
>>
>>> I think, this problem has been discussed on the list not long ago - `mt`
>>> being not found on the system after some MSVC update:
>>>
>>> Looks like MSVC needs to be reinstalled or installed on a separate
>>> machine. Will you be able to fix this?
>>
>> Most likely the path to the SDK tools is missing in the setup:
>> "C:\Program Files (x86)\Windows Kits\10\bin\x64" or
>> "C:\Program Files (x86)\Windows Kits\10\bin\x86"
>>
>> Ciao
>>    Dani
>>
> 
> Hmm, those two paths exist but have very little in them. It looks like most
> of the SDK (including mt.exe) is in 10/bin/10.0.16299.0/[x86|x64]. Any idea
> if that is normal?

FWIW, on my system I have mt.exe and other tools in both 10\bin\x64 and 
10\bin\10.0.16299.0\x64. But I probably haven't installed the 
problematic MSVC update.