Re: [Boost-users] [release] Boost 1.69.0 Beta 1 Release Candidate 1

Subject: Re: [Boost-users] [release] Boost 1.69.0 Beta 1 Release Candidate 1
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-11-13 15:38:33

AMDG

On 11/12/2018 05:30 PM, Tom Kent via Boost-users wrote:
> <snip>
> Also numerous errors for many (all dlls?) of the libraries with msvc-14.0.
> They all look something like this:
> 
> <snip>
> msvc.manifest.dll
> bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll
> 'mt' is not recognized as an internal or external command,
> operable program or batch file.
> 
>         if exist
> "bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll.manifest"
> (
>             call "bin.v2\standalone\msvc\msvc-14.0\msvc-setup.bat" x86 >nul
>  mt -nologo -manifest
> "bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll.manifest"
> "-outputresource:bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll;2"
>         )
> 
> <snip>
> 
> I'm on the fence if we should continue supporting 8.0, so if that doesn't
> get fixed then no big deal. However the issue with (the build tool?) for
> 14.0 seems like a showstopper for this RC.
> 

I don't think anything has changed in Boost.Build that would
affect this.  Have you checked your msvc installation?  I
would suggest checking whether msvc-setup.bat is out-dated,
but you're running a clean build here, right?

Can you try forcing the original setup scripts:

  using msvc : 14.0 : : <rewrite-setup-scripts>off ;

In Christ,
Steven Watanabe