
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe via Boost Sent: 28 March 2019 15:50 To: Paul A. Bristow via Boost Cc: Steven Watanabe Subject: Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
AMDG
On 3/28/19 9:30 AM, Paul A. Bristow via Boost wrote:
<snip> I don't think that vswhere.exe is visible from my user or VS command prompts :-(
<snip>
But one copy is present at C:\Program Files (x86)\Microsoft Visual Studio\Installer and
That's the right one.
With no parameters vswhere outputs this
C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved.
instanceId: bd686eb9 installDate: 10Dec2018 16:18:55 installationName: VisualStudio/15.9.10+28307.557 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional installationVersion: 15.9.28307.557 <snip>
I'm installing some other Visual Studio items to see if that will help.
It didn't. But I did notice that vswhere does not find vs2019 at all with the option -all, but vswhere *does* find both VS2017 and VS2019 with -prerelease option. So have I jumped the gun by prematurely installing the preview? Does msvc.jam need this adding to the list of options? I:\modular-boost\tools\build\src\tools\msvc.jam local vmwhere_cmd = "\"$(vswhere)\" -latest -products * $(req) $(prop) $(limit)" ; perhaps? but there are also some assumptions about 15.0 builtin, so perhaps I am entering where angels fear to tread. (assuming it is agreed that we want to find preview versions?) Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830