On Thu, Mar 23, 2017 at 8:51 PM, Rene Rivera via Boost
On Thu, Mar 23, 2017 at 2:37 PM, Olaf van der Spek via Boost < boost@lists.boost.org> wrote:
On Thu, Mar 23, 2017 at 5:36 PM, Mateusz Loskot
wrote: On 23 March 2017 at 17:04, Olaf van der Spek via Boost
wrote: VS2015 / W10:
boost_1_64_0>bootstrap.bat
Building Boost.Build engine HRESULT was unexpected at this time.
bootstrap.bat bootstrap.bat vc14 bootstrap.bat vc141
All succeed for me on W10 w/ VS2015 and VS2017
VS2017 / W7:
PS C:\vc\boost_1_64_0> .\bootstrap.bat 'cl' is not recognized as an internal or external command, operable program or batch file.
It's a know issue with the vs2017 detection code and the powershell version. If you can manage to update to a powershell >= 3 it should work.
Is PS3 required even if cl is already in the path via the dev prompt shortcut? And what about the VS2015 / W10 failure? -- Olaf