On Wed, Apr 5, 2017 at 9:12 PM, Rene Rivera via Boost wrote: On Tue, Apr 4, 2017 at 4:13 PM, Rene Rivera 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. That doesn't help us for the installs of VS2017 that are already out there
and may not see updates. We definitely can't depend on users getting the VS
update in a timely manner.
Tom