Subject: Re: [boost] [release] 1.64.0 please test master snapshot
From: Jürgen Hunold (jhunold_at_[hidden])
Date: 2017-03-22 09:11:28
Am Dienstag, 21. März 2017, 22:37:32 CET schrieb Rene Rivera via Boost:
> On Tue, Mar 21, 2017 at 2:32 PM, Jürgen Hunold via Boost <
> > Manually calling the helper script "cl_path.cmd" results in:
> > cl_path.cmd 14.10 -PathToCompiler
^^ please note the correct invocation.
> Works for me:
> 14.10 -PathToCompiler
> Although giving it an "invalid" version confuses it:
> Is that what you are doing?
No, I took care to do exactly as msvc.jam does. I've checked my build server
at work and the auto-detection fails there as well.
I've got failures on
Windows 7 64bit
Windows Server 2008 R2 Service Pack 1 64 bit
Both system running a German windows version with an English language pack
only Visual Studio 2017 Enterprise installation.
Compiling from a "Visual Studio Command Prompt for VS2017" works because the
compiler is already in the PATH.
Compiling from a vanilla cmd prompt does not work because the helper script
errors out as described earlier.
-- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold_at_gmx.eu ! Germany