6 Apr
2017
6 Apr
'17
6:29 a.m.
On Thu, Apr 6, 2017 at 4:12 AM, Rene Rivera via Boost
On Tue, Apr 4, 2017 at 4:13 PM, Rene Rivera
wrote: We just ask users to run the bootstrap/build from the VS command prompt which defines VS150COMNTOOLS. That way we can use the existing logic we have for that. And the user doesn't have to install mystery executables. When Microsoft fixes this mess we can support their fix.
Two updates..
* I implemented the build changes to just use VS150COMNTOOLS, and ProgramFiles env vars for detection. Although I haven't implemented the "ask users" part of this. * MS is going to include vswhere in an upcoming VS update in a known location.
Please test latest Boost snapshots and Boost Build.
Link?