Releases: metastack/msvs-tools
Releases · metastack/msvs-tools
MSVS Tools 0.8.0
MSVS Tools 0.7.0
- Various shellcheck overhauls and other hardening (#16, @dra27)
- Preview versions of Visual Studio are now included in results (#17, @dra27)
- New options
--installedand--output=data(#17, @dra27) - Various fixes to environment compiler detection and results (#17, @dra27)
- opam packaging for
msvs-detectexposed asconf-msvc32andconf-msvc64packages (#18, @dra27)
MSVS Tools 0.6.0
MSVS Tools 0.5.0
- Use
MSYS2_ARG_CONV_EXCLto disable MSYS2 argument mangling, replacing the workaround in 0.4.0 (#8, @jonahbeckford) - Handle special characters in
PATHinmsvs-promote-path. In particular, stray double-quote characters don't corrupt the command line. (#10) - Fix strong/weak detection of the environment compiler (#9, @jonahbeckford)
- Fix the vswhere invocation to detect Build Tools (#9, @jonahbeckford)
MSVS Tools 0.4.1
- Apply various fixes and clarifications from shellcheck (#7, @MisterDA)
- Improve tail-stripping of
MSVS_PATHto prevent path blow-out, especially when run from within a developer command prompt (or whenmsvs-detectis invoked recursively). - Ensure
PATH-mangling never overrides Cygwin bin (in particular, ensurewhichis always from the same Cygwin as the script)
MSVS Tools 0.4.0
Bug fixes for msvs-detect:
- Visual Studio 2019 will now be selected by default
- The script now works inside MSYS2, which previously was treating the switches in
cmd /v:on /cas MSYS2-style paths - The environment compiler is excluded if
LIBandINCLUDEare invalid (i.e. if the user has manually addedcl.exetoPATH).
MSVS Tools 0.3.2
Commands tested by msvs-promote-path can no longer leak output to stderr.
Bug fixes for msvs-detect:
- Visual Studio 2017 detection worked, but was not useful since updates increment the version number (so Visual Studio 2017 Update 5 is 15.5 whereas Visual Studio 2015 Update 3 is still 14.0). This has been fixed by allowing wildcards in
MSVS_PREFERENCEsoVS15.*means to select the most recent installed update of Visual Studio 2017. It is possible to specify specific updates (e.g.VS15.5) for particularly niche uses. - Escaping of special characters was broken inasmuch as it was completely missing.
--output=shellwill now correctly escape directory names which nefariously include a single quote and--output=makewill now escape both#and$meaning that the directory names of certain programming languages containing musical symbols in their names no longer unexpectedly comment out Makefile lines. - Strings for
--output=makewere being unnecessarily assigned to variables using:=and also incorrectly double-quoted.
MSVS Tools 0.3.1
One case missed for the Cygwin \r change in msvs-detect
MSVS Tools 0.3.0
msvs-detect updated to support Visual Studio 2017. Detection is done via vswhere which is automatically installed for Update 2 and later. Detection of the original release and Update 1 requires vswhere.exe to be downloaded and placed with the script.
msvs-detect works correctly with newer Cygwin tools which no longer strip \r from the output of native executables.
MSVS Tools 0.2.0
MSVS_NAME is now included in the output of msvs-detect which describes the software package providing the compiler selected.