stuartmorgan aecf053ee0 Use vswhere to find Visual Studio (#33448) ... Rather than hard-coding a set of locations to check, use vswhere (which is installed by VS 2017 and later), and construct the vcvars64.bat path relative to that. This will allow Windows builds to work without special configuration for people who have VS installed at a custom path. Also adds error logging with different messages for each failure point, so that rather than the not-very-informative 'failed to find vcvars64.bat' message, the failure will provide feedback about what to do. This is an interim solution; later this will be replaced by a VisualStudio class with associated validator to match the structure of the other toolchains. Fixes #33249		2019-05-29 09:17:17 -07:00
..
src	Use vswhere to find Visual Studio (#33448)	2019-05-29 09:17:17 -07:00
executable.dart	Teach Linux to use local engine (#31631)	2019-05-11 00:08:29 -07:00
runner.dart	don't send crash reports if on a user branch (#33078)	2019-05-21 11:58:41 -07:00